Most external-command detections are Markdown fence false positives, not executable backtick usage. The skill still contains high-risk authentication attack workflows, including brute-force testing, credential-stuffing evasion, MFA bypass, session fixation, JWT forgery, and password-reset account takeover techniques. Publication should require stronger authorization gating and removal or narrowing of offensive execution guidance.
The line is part of a Hydra form-based login attack command using username and password payload markers. This enables credential brute-force testing and is dangerous without authorization.
The skill provides brute-force and credential-stuffing procedures, including Hydra usage, breached credential pairs, and source IP or user-agent rotation guidance.
The cited sections explicitly cover brute force testing, credential stuffing, credential payloads, and lockout bypass via IP rotation. Authorization language exists, but the procedures are directly usable for account attack workflows.
The skill instructs OTP brute forcing, direct URL MFA skipping, response manipulation, empty OTP submission, OTP reuse, and API version downgrade testing.
The MFA section lists multiple concrete bypass methods and payload strategies. These are legitimate in a lab, but harmful if applied outside authorized scope.
The skill describes session fixation and password reset token manipulation workflows that can transfer or reset another user account.
The cited sections describe fixed-session victim login and changing reset user parameters. These are clear account takeover paths when controls are vulnerable.
The skill walks through modifying a JWT to use the none algorithm, changing the role to admin, and submitting the modified bearer token.
The example gives a complete token forgery flow with role escalation and replay. It is clearly a security test, but it is operationally useful for unauthorized privilege escalation.
# Compare responses for valid vs invalid usernames
The line instructs comparing valid and invalid username responses. This is username enumeration testing and can disclose account existence if used against an unauthorized target.
The recovery-process section asks whether MFA can be disabled via email alone. This is a valid security test, but it also identifies account recovery bypass opportunities.
The credentials appear inside a session fixation validation flow. It can be legitimate with test accounts, but it still supports checking whether a fixed session remains usable after login.
Capability review items (14)
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 adds an admin email parameter to a reset token to test account takeover. This is a concrete password reset abuse pattern despite using a placeholder host.
The IP appears in a list of spoofed forwarding headers for rate-limit bypass testing. This can help evade account lockout or throttling controls if misused.
The IP appears in a spoofed client IP header for rate-limit bypass testing. This can help evade throttling controls when applied to a vulnerable target.
The IP appears in a client IP header used for rate-limit bypass testing. The technique can weaken brute-force defenses when a target trusts the header.
The Python example uses requests in a loop to collect session cookies from a login URL. This is expected for scoped testing, but it can generate network traffic against a target if executed.
The hardcoded login URL appears inside a runnable HTTP request example. It is a placeholder, but it demonstrates live requests to an authentication endpoint.
The URL is part of a session fixation attack scenario that sends a fixed session value to a victim. The host is illustrative, but the workflow is an account takeover technique.
The reset URL is used to demonstrate token and user parameter manipulation. It is a placeholder, but the surrounding workflow tests password reset abuse.
The reset link is used as an example token for password reset exploitation testing. The domain is illustrative, but the workflow can be harmful outside authorization.
Most external-command detections are Markdown fence false positives, not executable backtick usage. The skill still contains high-risk authentication attack workflows, including brute-force testing, credential-stuffing evasion, MFA bypass, session fixation, JWT forgery, and password-reset account takeover techniques. Publication should require stronger authorization gating and removal or narrowing of offensive execution guidance.
The line is part of a Hydra form-based login attack command using username and password payload markers. This enables credential brute-force testing and is dangerous without authorization.
The skill provides brute-force and credential-stuffing procedures, including Hydra usage, breached credential pairs, and source IP or user-agent rotation guidance.
The cited sections explicitly cover brute force testing, credential stuffing, credential payloads, and lockout bypass via IP rotation. Authorization language exists, but the procedures are directly usable for account attack workflows.
The skill instructs OTP brute forcing, direct URL MFA skipping, response manipulation, empty OTP submission, OTP reuse, and API version downgrade testing.
The MFA section lists multiple concrete bypass methods and payload strategies. These are legitimate in a lab, but harmful if applied outside authorized scope.
The skill describes session fixation and password reset token manipulation workflows that can transfer or reset another user account.
The cited sections describe fixed-session victim login and changing reset user parameters. These are clear account takeover paths when controls are vulnerable.
The skill walks through modifying a JWT to use the none algorithm, changing the role to admin, and submitting the modified bearer token.
The example gives a complete token forgery flow with role escalation and replay. It is clearly a security test, but it is operationally useful for unauthorized privilege escalation.
# Compare responses for valid vs invalid usernames
The line instructs comparing valid and invalid username responses. This is username enumeration testing and can disclose account existence if used against an unauthorized target.
The recovery-process section asks whether MFA can be disabled via email alone. This is a valid security test, but it also identifies account recovery bypass opportunities.
The credentials appear inside a session fixation validation flow. It can be legitimate with test accounts, but it still supports checking whether a fixed session remains usable after login.
Capability review items (14)
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 adds an admin email parameter to a reset token to test account takeover. This is a concrete password reset abuse pattern despite using a placeholder host.
The IP appears in a list of spoofed forwarding headers for rate-limit bypass testing. This can help evade account lockout or throttling controls if misused.
The IP appears in a spoofed client IP header for rate-limit bypass testing. This can help evade throttling controls when applied to a vulnerable target.
The IP appears in a client IP header used for rate-limit bypass testing. The technique can weaken brute-force defenses when a target trusts the header.
The Python example uses requests in a loop to collect session cookies from a login URL. This is expected for scoped testing, but it can generate network traffic against a target if executed.
The hardcoded login URL appears inside a runnable HTTP request example. It is a placeholder, but it demonstrates live requests to an authentication endpoint.
The URL is part of a session fixation attack scenario that sends a fixed session value to a victim. The host is illustrative, but the workflow is an account takeover technique.
The reset URL is used to demonstrate token and user parameter manipulation. It is a placeholder, but the surrounding workflow tests password reset abuse.
The reset link is used as an example token for password reset exploitation testing. The domain is illustrative, but the workflow can be harmful outside authorization.
Static command execution and network findings are mostly Markdown examples, not executable package code, so those scanner hits are false positives for embedded malware. The skill is still high risk because it gives actionable brute force, credential stuffing, MFA bypass, lockout bypass, and account takeover testing workflows, including evasion tactics. No prompt injection attempt was found in SKILL.md.
1
Files scanned
482
Lines analyzed
8
Review items
1
False positives ignored
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Actionable Brute Force and Credential Stuffing Guidance
The skill instructs users to run password guessing and credential stuffing tests, including Hydra usage, breached credential lists, and detection evasion tactics such as rotating source IPs and randomizing user agents. This is dual-use content that can enable unauthorized account compromise if used outside a written test scope.
The cited sections explicitly describe brute force tooling, breached credential inputs, and evasion behavior. The skill includes authorization language, so malicious intent is not confirmed, but the abuse potential is clear.
Authentication Bypass and Token Tampering Playbooks
The skill provides step-by-step testing for OTP bypass, direct MFA step skipping, response manipulation, JWT none algorithm abuse, and submission of modified authorization tokens. These workflows are actionable exploitation guidance for account privilege escalation.
The semantic context confirms exploitation workflows, not just abstract vulnerability descriptions. The examples are framed as testing, which keeps this below confirmed malicious intent.
The skill describes session fixation, password reset token manipulation, host header injection in reset flows, and changing reset parameters toward another account. These examples can guide unauthorized access if copied against real services.
The cited material gives concrete account takeover scenarios and parameter manipulation steps. Authorization constraints are present elsewhere, so this is high risk rather than confirmed malicious.
The skill includes examples that send HTTP requests to target applications and collect session cookies. These are expected for security testing, but they require explicit scope controls and could affect real systems if used carelessly.
The network behavior is documented in examples and appears intended for authorized assessment. Risk remains because the examples interact with authentication endpoints and session state.
Markdown Code Fence Detected as Ruby Backtick Execution
The static analyzer flagged many fenced Markdown blocks as Ruby or shell backtick execution. SKILL.md is documentation and no executable Ruby file or package script is present, so these detections are false positives for embedded command execution.
The flagged patterns appear inside Markdown code fences or prose examples. No evidence of executable Ruby backtick calls was found in the only scanned file.
Placeholder URLs and IP Headers Detected as Network Indicators
Hardcoded URLs and IP addresses are placeholder target examples and HTTP header examples, not evidence of calls to attacker-controlled infrastructure. They still indicate that the skill teaches network-facing authentication tests.
The URLs use generic target.com examples and the IP addresses are local or private header values. This supports a false positive for exfiltration or command-and-control infrastructure.
Static false positives ignored (1)
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.
Weak Crypto and C2 Keyword Matches Are Contextual False Positives
Static matches for weak cryptography and C2 keywords appear in authentication testing context, such as JWT algorithm testing and bearer token examples. No evidence found of malware, command-and-control behavior, or cryptographic implementation code.
The suspicious strings are documentation examples for authentication weaknesses. The file contains no runnable cryptographic library implementation or C2 client.
This is a legitimate security education skill for testing authentication vulnerabilities. All static findings are false positives - the skill contains documentation and examples showing testing methodologies, not malicious code. The skill explicitly requires written authorization and is designed for authorized security testing professionals.
1
Files scanned
482
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.