Generate ONE strong password and apply it to each referenced file (PDF, Word, Excel, PowerPoint, or any type). Use when asked to password-protect / encrypt / lock one or more deliverable files with a single password before sharing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Mint a single strong password and password-protect every referenced file with it, "accordingly" per file type. Deterministic, non-destructive (originals are never touched), AES-256 or nothing.
python3 tools/protect_with_password.py FILE [FILE ...] \
[--password PW] [--length 24] [--out-dir DIR] \
[--password-file PATH | --no-password-file]
--password overrides to reuse one).--out-dir.--no-password-file) writes the password to a chmod-600 PROTECT-PASSWORD.txt.| File | Protection | Result |
|---|---|---|
.pdf | Native AES-256 (qpdf → pypdf fallback) | <name>-protected.pdf — recipient is prompted for the password on open |
.docx/.xlsx/.pptx, .doc/.xls/.ppt, images, anything else | AES-256 7-Zip archive (-mhe=on, filenames encrypted) | <name>.7z — recipient extracts with the password (7-Zip / Keka / WinRAR) |
Native in-file Office (MS-OFFCRYPTO "agile") encryption needs LibreOffice or a dedicated encryptor that is not bundled here, so Office files are wrapped in a strong AES-256 archive instead. If no AES-256 tool is available for a file, it is reported as a failure — never downgraded to weak ZipCrypto/RC4 (no false assurance).
Relay the password to the user and remind them to share it OUT-OF-BAND — never in the same channel/email as the protected files — and to delete PROTECT-PASSWORD.txt once handed over. Exit code is 0 only if every file was protected; 1 if any failed (check results[].reason).
Related: tools/protect_deliverable.py does the engagement-wide variant (one protected PDF + an AES-256 deliverable zip); this skill protects an arbitrary set of individual files.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Offensive AI security testing and exploitation framework. Systematically tests LLM applications for OWASP Top 10 vulnerabilities including prompt injection, model extraction, data poisoning, and supply chain attacks. Integrates with pentest workflows to discover and exploit AI-specific threats.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
API security testing - GraphQL, REST API, WebSocket, and Web-LLM attack techniques.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stitches confirmed single-asset findings into multi-hop attack paths across the organization. Builds a graph where nodes are assets and edges are confirmed exploit hops citing the findings that enable them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Acquire an authenticated session THROUGH MFA/OTP on an in-scope target and emit a reusable session artifact (Playwright storageState + Bearer) so executors can test the post-auth attack surface. Use when the highest-value authenticated classes (BOLA/IDOR/mass-assignment/injection on the real data APIs) are blocked because login is gated by SMS-OTP or TOTP MFA. Distinct from the authentication skill (which ATTACKS auth); this one legitimately authenticates and hands the session to the rest of the engagement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Authentication security testing - auth bypass, JWT attacks, OAuth flaws, password attacks, 2FA bypass, CAPTCHA bypass, and bot detection evasion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Smart contract security testing and blockchain CTF exploitation. Covers Solidity vulnerability analysis, EVM storage manipulation, delegatecall attacks, CREATE/CREATE2 address prediction, and common DeFi exploit patterns. Use when analyzing Solidity contracts, solving blockchain challenges, or testing smart contract security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.