storage-san-attack
Audited by Socket on Sep 19, 2026
5 alerts found:
Securityx3MalwareAnomalySUSPICIOUS/HIGH-RISK skill. It is internally consistent with its stated purpose, but that purpose is to equip an AI agent with offensive storage intrusion, credential harvesting, and ransomware-simulation workflows. There is little evidence of hidden exfiltration or deceptive install behavior, yet the autonomous offensive capability and direct instructions for destructive and data-theft actions make the overall security risk high.
The visible fragment is an overt storage attack and ransomware playbook, not benign dependency functionality. It documents credential attacks, secret harvesting, webshell deployment, data extraction, privilege-impacting writes, ransomware workflows, snapshot/object destruction, and anti-forensic actions. Labels such as authorized testing and placeholders provide context but do not make the commands safe. There is no clear obfuscation or covert npm malware mechanism in this excerpt, but the operational security risk is extremely high if executed against real systems.
This fragment is an authorized storage penetration-testing playbook, not malicious package code. It documents dual-use and potentially destructive techniques, including NTLM relay, credential/hash use, data acquisition, packet capture, and access-policy modification. These create operational and privacy risks when used without authorization, but there is no evidence here of malware, persistence, credential exfiltration to a covert destination, or sabotage logic. Review and restrict execution to explicitly scoped engagements.
This fragment is an overt dual-use storage security and penetration-testing guide, not an obfuscated software payload. It contains high-impact offensive procedures and credential-handling examples, including an explicit XSS cookie exfiltration demonstration, but no evidence of autonomous malicious behavior or package-level malware. Use is restricted to authorized environments; the content presents a significant misuse and operational security risk.
This fragment is an offensive storage-security testing playbook, not evidence of npm-style malware by itself. It contains several high-impact procedures, especially webshell deployment, credential harvesting, SNMP configuration writes, and mass S3 encryption. Those actions are potentially authorized in a controlled penetration test but pose an extremely high operational security risk if executed without explicit scope and safeguards. No intentional package malware or obfuscation is evident from the displayed documentation fragment.