This report does not block or authorize the manifest or ZIP.
AI adjudication confirmed live WordPress reconnaissance, user enumeration, credential brute force, Metasploit exploitation, reverse shells, webshells, XML-RPC abuse, proxy scanning, and evasion. Several Markdown-only backtick and path detections were false positives, but the skill intent remains offensive and high risk. It should not be published for automatic agent use without removing exploitation, brute-force, backdoor, and evasion material.
Report position
Historical report
Open audit history before using this report to install.
Audit attestation
Not attestable
The required immutable binding is incomplete.
Human verification
Not verified
No human verification is recorded for this report.
Coverage
1 Files scanned · 486 Lines analyzed
106 items shown for review
Limitations
This report does not claim runtime or sandbox execution and does not prove the absence of side effects.
01
Evidence chain
Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.
The line uses PHP exec to launch an interactive bash reverse shell to an operator-controlled IP placeholder. This is direct remote code execution, not a benign script helper.
The line runs PHP exec to launch an interactive bash reverse shell to an operator-controlled IP placeholder. This is direct remote code execution and post-compromise access.
This command block walks through Metasploit WordPress exploit modules, credential setup, listener configuration, and exploit execution. It is concrete exploitation guidance.
This command block walks through Metasploit WordPress exploit modules, credential setup, listener configuration, and exploit execution. It is concrete exploitation guidance.
This bash block creates a malicious WordPress plugin containing a request-controlled system command webshell, zips it, and accesses it remotely. It is concrete webshell construction.
The line runs PHP exec to launch an interactive bash reverse shell to an operator-controlled IP placeholder. This is direct remote code execution and post-compromise access.
The URL appears in the exploitation section and supports reverse shell or webshell access after uploading malicious WordPress code. The target.com value is a placeholder, but the behavior is remote command execution.
The URL appears in the exploitation section and supports reverse shell or webshell access after uploading malicious WordPress code. The target.com value is a placeholder, but the behavior is remote command execution.
This bash block enumerates WordPress users through WPScan, author IDs, REST APIs, and login errors. Username enumeration increases the feasibility of later credential attacks.
This bash block builds XML-RPC multicall requests with candidate passwords and posts them to WordPress. It enables authentication abuse and brute-force behavior.
This bash block configures WPScan traffic through Tor, HTTP, and Burp proxies, including TLS check disabling. It supports proxied and evasive scanning.
The quick reference includes a runnable WPScan password attack command. It is a concise credential attack example, not just documentation of a harmless flag.
This line is Markdown inline code, but it appears in a Detection Evasion section recommending random user agents or throttling. That context supports avoiding monitoring during scans.
This line is Markdown inline code, but it appears in a Detection Evasion section recommending random user agents or throttling. That context supports avoiding monitoring during scans.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
This line sends XML-RPC requests to a WordPress endpoint, including method discovery and multicall password testing. In context it enables abusive authentication probing.
curl -X POST -d '<?xml version="1.0"?><methodCall><methodName>system.listMethods</methodName></metho
This line sends XML-RPC requests to a WordPress endpoint, including method discovery and multicall password testing. In context it enables abusive authentication probing.
curl -X POST -d @xmlrpc_brute.xml http://target.com/xmlrpc.php
This line sends XML-RPC requests to a WordPress endpoint, including method discovery and multicall password testing. In context it enables abusive authentication probing.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
This line is part of a credential brute-force workflow using usernames, password lists, or XML-RPC attack modes. That enables account compromise against any supplied WordPress target.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
The loopback IP is a local proxy endpoint, not a hidden remote server. In this skill it is used for proxied WPScan traffic and TLS-check disabling, which supports evasive scanning.
Although the matched token is a Markdown bash fence, the finding spans a runnable command block for WordPress discovery, enumeration, or vulnerability scanning. These commands can affect live targets.
Although the matched token is a Markdown bash fence, the finding spans a runnable command block for WordPress discovery, enumeration, or vulnerability scanning. These commands can affect live targets.
Although the matched token is a Markdown bash fence, the finding spans a runnable command block for WordPress discovery, enumeration, or vulnerability scanning. These commands can affect live targets.
Although the matched token is a Markdown bash fence, the finding spans a runnable command block for WordPress discovery, enumeration, or vulnerability scanning. These commands can affect live targets.
This command block uses exploit search tooling in the WordPress exploitation workflow. It can support legitimate triage, but in context it helps identify offensive exploit paths.
Although the matched token is a Markdown bash fence, the finding spans a runnable command block for WordPress discovery, enumeration, or vulnerability scanning. These commands can affect live targets.
This command block uses exploit search tooling in the WordPress exploitation workflow. It can support legitimate triage, but in context it helps identify offensive exploit paths.
Although the matched token is a Markdown bash fence, the finding spans a runnable command block for WordPress discovery, enumeration, or vulnerability scanning. These commands can affect live targets.
This bash block contains authenticated WPScan and TLS-check disabling examples. It is legitimate in scope but risky because it directs live scanning behavior.
The quick reference contains runnable WPScan commands for live target enumeration or aggressive detection. This is active scanning behavior requiring authorization.
| All enumeration | `wpscan --url http://target.com -e at,ap,u` |
The quick reference contains runnable WPScan commands for live target enumeration or aggressive detection. This is active scanning behavior requiring authorization.
The quick reference contains runnable WPScan commands for live target enumeration or aggressive detection. This is active scanning behavior requiring authorization.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
This WPScan command uses an API token placeholder and performs vulnerability data lookups against a target site. It is not secret exfiltration, but it is active network assessment behavior.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
curl -s http://target.com/readme.html | grep -i version
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
wpscan --url http://target.com -e at --plugins-detection aggressive
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
curl -s http://target.com/wp-content/themes/<theme>/style.css | grep -i version
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
wpscan --url http://target.com -e ap --plugins-detection aggressive
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
wpscan --url http://target.com -e ap --plugins-detection mixed
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
curl -X POST -d "log=admin&pwd=wrongpass" http://target.com/wp-login.php
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
The URL is a placeholder rather than a hidden exfiltration endpoint, but the command performs active WordPress reconnaissance against a target site. This must be restricted to authorized scope.
This WPScan example performs authenticated or TLS-modified scanning against a live target placeholder. It is legitimate in a scoped test but risky if run without authorization.
This WPScan example performs authenticated or TLS-modified scanning against a live target placeholder. It is legitimate in a scoped test but risky if run without authorization.
The quick reference contains runnable WPScan commands for live target enumeration or aggressive detection. The placeholder URL does not remove the network scanning risk.
| All enumeration | `wpscan --url http://target.com -e at,ap,u` |
The quick reference contains runnable WPScan commands for live target enumeration or aggressive detection. The placeholder URL does not remove the network scanning risk.
The quick reference contains runnable WPScan commands for live target enumeration or aggressive detection. The placeholder URL does not remove the network scanning risk.
03
Risk findings
Confirmed security concerns are separated from items that still need review.
The skill requires and demonstrates Metasploit use for WordPress shell upload and exploitation. This is a real offensive capability that can compromise a target host.
The skill requires and demonstrates Metasploit use for WordPress shell upload and exploitation. This is a real offensive capability that can compromise a target host.
The skill requires and demonstrates Metasploit use for WordPress shell upload and exploitation. This is a real offensive capability that can compromise a target host.
The line recommends a weevely backdoor in the manual exploitation section. That is malware-style persistence and command access, not a benign assessment artifact.
The line appears under Detection Evasion and advises avoiding aggressive modes on monitored sites. This supports stealthier reconnaissance rather than only safe rate control.
The skill requires Nmap and provides a WordPress detection scan command. Network scanning is legitimate in authorized tests but dangerous against third-party systems.
The skill requires Nmap and provides a WordPress detection scan command. Network scanning is legitimate in authorized tests but dangerous against third-party systems.
The skill requires Nmap and provides a WordPress detection scan command. Network scanning is legitimate in authorized tests but dangerous against third-party systems.
The skill includes a Detection Evasion section recommending random user agents, throttling, proxy rotation, and avoiding aggressive modes on monitored sites.
The heading and bullets directly frame these options as evasion, which increases misuse risk beyond ordinary rate control guidance.
04
Remediation
Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.
FIX-001
Critical
Metasploit and shell-upload exploitation guidance
Remove Metasploit modules, exploit execution steps, reverse shell commands, and shell access deliverables. Replace them with defensive validation and remediation guidance.
FIX-002
Critical
Malicious plugin and webshell construction
Remove instructions that create request-controlled command execution or backdoor plugins. Use safe proof artifacts that cannot execute commands.
FIX-003
High
Credential brute-force workflows
Remove WPScan password attack examples, XML-RPC brute-force payloads, and wordlist generation steps. Focus on password policy review and controlled lab notes.
FIX-004
High
Proxy and detection evasion advice
Remove Tor proxy, proxy rotation, random user agent, WAF bypass, and monitored-site evasion guidance. Keep only load-reduction and scope-control advice.
FIX-005
Medium
Unscoped live target commands
Add mandatory authorization checks and replace public target placeholders with local lab hostnames. Separate safe read-only assessment from exploit demonstrations.
05
Expert evidence
Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.
Artifact subject
Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable
Analysis metadata
Audit model: codex
Analysis state: Complete
Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.