red-team-infrastructure
Audited by Socket on Sep 19, 2026
4 alerts found:
Malwarex4HIGH RISK. The skill is internally consistent with its stated purpose, but that purpose is to operationalize stealthy offensive C2 infrastructure and evasive tradecraft. It enables impactful autonomous actions, covert external data flows, destructive teardown, and reduced-review execution paths; this is not confirmed malware, but it is an unsafe offensive-security skill for an AI agent.
This fragment is highly indicative of malicious command-and-control infrastructure and implant operations. It contains covert traffic forwarding, command retrieval, payload generation, evasion, infrastructure provisioning, credential use, and evidence-destruction procedures. It should be treated as dangerous and unsuitable for inclusion in a normal open-source dependency or production software supply chain.
This is a highly actionable offensive C2 and evasion runbook. It documents deployment of implants and command-and-control systems, concealment through redirectors and domain fronting, attribution avoidance, and destruction of forensic evidence. While it could support authorized red-team work, the explicit stealth, victim execution, stolen-payment, operator-anonymity, and log-wiping procedures create a high likelihood of misuse and significant security risk. The supplied fragment is documentation rather than executable malware, but it describes workflows commonly used for unauthorized remote control and persistence.
The visible content is a high-risk offensive C2 infrastructure and implant-deployment playbook. It contains clear command-and-control, evasion, dead-drop, monitoring, and anti-forensic patterns. Although it may be intended for authorized red-team work, the procedures are directly usable for malware operations and unauthorized persistence. No package-runtime malware mechanism is visible because this is documentation rather than executable library code.