terminal-ops
Audited by Socket on Sep 19, 2026
4 alerts found:
Securityx2Anomalyx2SUSPICIOUS. The skill is internally coherent as an offensive security workflow, and I see no hidden installer, credential harvesting, or third-party data exfiltration. However, its stated purpose is to enable AI-guided penetration testing, exploitation, post-exploitation, stealth, and environment changes, which makes it a high-risk offensive capability for an agent even though the specific scanner findings are benign documentation artifacts.
The fragment is an offensive penetration-testing playbook with commands capable of reverse shells, exploitation, credential collection, lateral movement, interception, and remote execution. It presents substantial operational security risk if executed without authorization and contains unsafe command-construction patterns. However, the visible portion is documentation/examples with placeholders and provides no direct evidence of npm supply-chain malware, automatic execution, persistence, or covert exfiltration.
The fragment is an explicit authorized penetration-testing and evidence-management procedure, not apparent npm malware. It contains high-impact reconnaissance and exploit instructions, including a path-traversal request intended to retrieve /etc/passwd, plus broad scanning and /tmp cleanup operations. These create operational and authorization risks if executed improperly, but the fragment shows no concealed malicious behavior or supply-chain backdoor. Review execution controls, target authorization, cleanup scope, and evidence-integrity handling before use.
The fragment is a dual-use terminal network operations guide. It contains potentially dangerous reconnaissance, packet-capture, tunneling, relay, file-transfer, and reverse-shell-listener instructions, but no embedded malware or automatic malicious behavior. Use should be restricted to authorized systems and networks; packet captures and transferred files may contain sensitive data.