payload-generation
Audited by Socket on Sep 19, 2026
11 alerts found:
Malwarex5Securityx6High-risk offensive skill. Its capabilities are internally consistent with its stated purpose, but that purpose is to help an AI agent create and deliver exploitation payloads, reverse shells, and C2 channels. No strong evidence of hidden credential theft or obfuscation in the skill text itself, yet the operational footprint is inherently dangerous and unsuitable for general agent use.
The fragment is a high-risk offensive payload-generation and evasion guide. It creates reverse shells, encrypts and obfuscates shellcode, executes decrypted memory, supports host-gated targeting, and optimizes payloads against AV/YARA detection. It is not evidence of a benign package utility and should be treated as malicious or unauthorized unless clearly isolated to an explicitly authorized penetration-testing project.
The fragment contains an explicit automated reverse-shell and Meterpreter payload-generation pipeline for multiple platforms, along with guidance for execution and macOS security-control bypass testing. It does not show npm lifecycle execution or hidden package-install behavior, and the content may be intended for authorized penetration testing, but the generated artifacts provide direct unauthorized remote-access capability. Treat the material as high-risk offensive tooling and do not include or execute it in a software supply-chain package without strict authorization and isolation.
The fragment is offensive-security documentation containing extensive reverse-shell, payload-generation, delivery, command-execution, and evasion instructions. It presents significant misuse and operational security risk if distributed to or executed by unauthorized users, but the supplied Markdown itself does not automatically execute commands, exfiltrate data, install persistence, or perform network activity. It should be treated as high-risk dual-use content and restricted to authorized isolated testing environments.
This fragment contains extensive, actionable web-shell and reverse-shell code, including unauthenticated command execution, arbitrary file reads, outbound reverse connections, persistence concepts, and explicit WAF/antivirus evasion. As documentation it is not itself proof of active malware execution, but inclusion in an otherwise unrelated software package would be a severe supply-chain warning and should be treated as potentially malicious until the package context and provenance are verified.
The fragment contains an explicit PowerShell reverse shell and extensive documentation for payload generation, evasion, persistence, and remote command execution. The code is not merely suspicious: if executed and connected, it provides arbitrary command execution to a remote party. The text itself is documentation and does not execute solely by being present, so malware probability for the fragment as a passive file is lower than the operational danger of the supplied commands. The content should be treated as high-risk dual-use offensive tooling, and its origin and execution context should be investigated before inclusion or execution.
The supplied file is not executable package code and does not itself perform malicious actions. It is nevertheless a high-risk offensive security playbook containing actionable reverse-shell generation, remote payload delivery, PE injection, service/DLL/macro execution, and antivirus-evasion procedures. Use should be restricted to controlled, explicitly authorized environments; the document should not be treated as harmless dependency documentation.
This fragment contains explicit instructions and executable examples for phishing, payload delivery, reverse shells, AMSI bypass, process injection, credentialed WMI execution, and other defense-evasion techniques. It is highly suspicious and dangerous in a software supply-chain context, although the displayed portion is documentation and does not alone prove that the package automatically executes the commands. Review package scripts, postinstall hooks, and references to these snippets immediately.
The fragment is offensive security testing documentation, not ordinary application-library code. It does not by itself demonstrate that the package contains a hidden malware implant, but it generates and executes reverse shells and explicitly optimizes payloads to bypass antivirus detection. External upload of payloads and API credentials is an important data-handling risk. If included in an npm or other software package, these scripts and instructions would be highly anomalous and should be isolated, reviewed, and excluded from production distributions.
This fragment is an offensive security-testing utility that generates Windows reverse-shell and Meterpreter executables, including encoded variants, and provides instructions for executing them against a listener. It does not itself show data theft or persistence, but the generated payloads are inherently capable of unauthorized remote access and should only be used in an authorized isolated lab. The code is readable rather than heavily obfuscated, although it deliberately applies payload encoding.
The fragment provides explicit credential theft, malware delivery, reverse-shell control, watering-hole exploitation, deceptive UI, and campaign monitoring. It strongly indicates an offensive phishing and intrusion toolkit or training material designed to capture credentials and execute payloads. The code should not be used in production or against systems without explicit authorization.