Most external-command detections are false positives caused by Markdown code fences, not executable backtick usage. Several network and blocker findings are confirmed because the skill provides actionable guidance for credential attacks, rate-limit evasion, MFA bypass, session fixation, and password reset account takeover testing. No prompt injection attempt was found in SKILL.md.
The Hydra form string supports automated password attempts against a login endpoint. It is actionable brute-force guidance despite the authorized-testing framing.
The skill instructs testing with breached credential pairs and includes detection evasion steps such as slow rates, IP rotation, randomized user agents, and delays.
The guidance explicitly combines credential stuffing with evasion techniques. Written authorization is mentioned elsewhere, but the operational abuse content is clear.
The skill describes OTP brute force, direct MFA step skipping, response modification, OTP reuse, and API version downgrade testing to bypass MFA controls.
The cited section provides multiple concrete MFA bypass techniques and validation steps. These techniques are dual-use but clearly actionable.
The skill includes reset-token user manipulation, host header injection, and admin email parameter tampering to test whether another account can be reset.
The cited steps target password reset authorization and email routing flaws that can lead to account takeover. The examples are specific and operational.
The recovery-process checks can expose ways to disable MFA through account recovery. Legitimate testing is possible, but the business-logic abuse risk is real.
Capability review items (13)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The URL appears inside an attacker session-fixation workflow involving a victim login. This is actionable account takeover guidance if used outside an authorized lab.
The reset URL demonstrates changing a user parameter while using a valid reset token. That pattern can support password reset account takeover testing or abuse.
The reset URL changes the email parameter to an admin account and asks whether an admin password can be reset. This is direct account takeover guidance.
The Python example performs repeated HTTP requests to a target login endpoint to collect session tokens. This is expected security-testing behavior but still creates network activity against a target application.
The hardcoded URL is a placeholder in a copyable token-collection example. It is not a hidden callback, but it normalizes active requests against a login endpoint.
Most external-command detections are false positives caused by Markdown code fences, not executable backtick usage. Several network and blocker findings are confirmed because the skill provides actionable guidance for credential attacks, rate-limit evasion, MFA bypass, session fixation, and password reset account takeover testing. No prompt injection attempt was found in SKILL.md.
The Hydra form string supports automated password attempts against a login endpoint. It is actionable brute-force guidance despite the authorized-testing framing.
The skill instructs testing with breached credential pairs and includes detection evasion steps such as slow rates, IP rotation, randomized user agents, and delays.
The guidance explicitly combines credential stuffing with evasion techniques. Written authorization is mentioned elsewhere, but the operational abuse content is clear.
The skill describes OTP brute force, direct MFA step skipping, response modification, OTP reuse, and API version downgrade testing to bypass MFA controls.
The cited section provides multiple concrete MFA bypass techniques and validation steps. These techniques are dual-use but clearly actionable.
The skill includes reset-token user manipulation, host header injection, and admin email parameter tampering to test whether another account can be reset.
The cited steps target password reset authorization and email routing flaws that can lead to account takeover. The examples are specific and operational.
The recovery-process checks can expose ways to disable MFA through account recovery. Legitimate testing is possible, but the business-logic abuse risk is real.
Capability review items (13)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The URL appears inside an attacker session-fixation workflow involving a victim login. This is actionable account takeover guidance if used outside an authorized lab.
The reset URL demonstrates changing a user parameter while using a valid reset token. That pattern can support password reset account takeover testing or abuse.
The reset URL changes the email parameter to an admin account and asks whether an admin password can be reset. This is direct account takeover guidance.
The Python example performs repeated HTTP requests to a target login endpoint to collect session tokens. This is expected security-testing behavior but still creates network activity against a target application.
The hardcoded URL is a placeholder in a copyable token-collection example. It is not a hidden callback, but it normalizes active requests against a login endpoint.
The static backtick, URL, IP address, C2, and weak-crypto findings are mostly false positives caused by fenced Markdown examples and placeholder values. However, the skill gives operational guidance for brute force testing, credential stuffing, detection evasion, MFA bypass, JWT tampering, and reset-token abuse, so publication should require human review and stronger safety constraints.
1
Files scanned
477
Lines analyzed
7
Review items
2
False positives ignored
Capability review items (5)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The skill includes concrete workflows for brute force testing and credential stuffing, including Hydra usage, breached credential pairs, response analysis, and successful login detection. This is dual-use penetration testing content, but it can materially enable account takeover if used without authorization.
The lines explicitly describe automated login attacks and credential stuffing workflows. The document states authorization requirements elsewhere, but the attack steps are still operational.
Authentication Bypass and Token Tampering Playbook
The skill documents MFA bypass approaches, API downgrade testing, OTP brute force, JWT none-algorithm tampering, and bearer token submission. These techniques can support valid assessments, but they also provide direct bypass methods against real accounts.
The cited sections contain explicit bypass and token modification instructions. The context is security testing, but the instructions are directly actionable.
The skill advises IP rotation, user-agent randomization, delays, X-Forwarded-For bypass testing, and per-attempt IP changes. This guidance can help validate defenses, but it also teaches evasion of controls that protect login endpoints.
The content directly discusses bypassing lockouts and rate limits with source IP manipulation. This is high-risk even when presented as an authorized test.
Session Fixation and Password Reset Abuse Scenarios
The skill provides attack scenarios for fixed sessions, host header manipulation, reset-token user parameter changes, and resetting another user's password with a test token. These are valid test cases but expose sensitive abuse workflows.
The cited examples describe specific account takeover paths. The content remains framed as testing, so this is moderate to high dual-use risk rather than confirmed malicious intent.
The hardcoded URLs and IP addresses use placeholder domains or local/private addresses for test examples. I found no evidence that the skill sends data to an author-controlled endpoint.
The URLs point to target.com examples and the IPs are loopback or private examples. There is no author-controlled collection endpoint in the reviewed file.
Static false positives ignored (2)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Static Backtick Command Findings Are Mostly False Positives
The external command detector flagged many fenced Markdown blocks as Ruby or shell backtick execution. The reviewed file is documentation, not executable Ruby code, so these locations do not show direct command execution by the skill.
The flagged backticks are Markdown code fences, not language-level execution syntax. The examples are still high-risk by content, but not because the skill executes commands.
C2 and Weak-Crypto Static Blockers Are Contextual False Positives
The C2 keyword detections correspond to bearer tokens in JWT examples, and the weak-crypto detections appear in authentication terminology and JWT algorithm discussion. I found no evidence of malware control logic or implemented weak cryptography.
The suspicious tokens are part of explanatory web security examples. The file does not contain executable malware logic or cryptographic implementation code.
This is a legitimate penetration testing and security assessment skill. All 76 static findings are false positives: the detected 'external_commands' and 'network' patterns are documentation code examples showing legitimate security testing techniques (hydra commands, HTTP request examples, JWT attack demonstrations). The skill properly includes legal requirements for authorization and scope limitations. No actual executable malware or exploit code is present.