network-sniffing-mitm
Audited by Socket on Sep 19, 2026
5 alerts found:
Securityx2Anomalyx3SUSPICIOUS. The skill is internally consistent with its stated purpose, but that purpose is to give an AI agent concrete offensive network-attack capability: MITM, credential harvesting, traffic manipulation, evasion, and chaining into further exploitation. No strong malware indicators or hidden exfiltration endpoints appear in the text, but the operational attack guidance and enabled tool access make this a high-risk skill.
The fragment is an offensive security test-plan section, not executable malware. It documents techniques capable of credential capture, NTLM relay, MITM positioning, remote file creation, traffic manipulation, and token logging. These actions are high risk when executed without authorization, but the supplied text alone contains no implemented malicious behavior or supply-chain backdoor. Review and restrict distribution/use to authorized lab assessments, and ensure test credentials, targets, and captured authentication material are isolated.
The fragment contains explicit dual-use offensive networking instructions, including active DNS spoofing and credential-oriented packet sniffing. It does not itself demonstrate npm malware, persistence, automated exfiltration, or destructive behavior, and the visible material appears to be documentation/examples rather than package execution logic. It represents a significant security concern if shipped in an unrelated library or executed without authorization, but malware intent cannot be established from this fragment alone.
The fragment is security documentation containing highly actionable commands for offline NetNTLM password cracking and guidance for credential-harvesting operations. It presents significant dual-use and abuse risk, particularly because it discusses evasion and active poisoning, but the shown content is not itself malware and contains no executable implementation or evident data exfiltration. Authorization and surrounding file context should be verified before use.
The fragment is offensive security documentation containing actionable instructions for network interception, HTTPS downgrade, cookie exfiltration, session hijacking, and traffic injection. It does not itself demonstrate that an npm package automatically performs these actions, since the visible content consists of manually executed commands and examples. If distributed as documentation in a security-testing project, the behavior may be intentional and authorized; nevertheless, misuse potential and the explicit credential-exfiltration example create a substantial security concern.