kubernetes-attack
Audited by Socket on Sep 19, 2026
5 alerts found:
Securityx5SUSPICIOUS/HIGH-RISK offensive security skill. Its capabilities are aligned with its stated red-team purpose, but that purpose is to perform Kubernetes exploitation, credential theft, persistence, and cloud pivots. Install references are mostly legitimate project sources, so this is not confirmed malware, but it is a high-risk exploit skill for an AI agent with substantial potential for unauthorized compromise and exfiltration.
This fragment is a high-risk offensive Kubernetes attack guide, not apparent malware or executable supply-chain code. It contains actionable instructions for credential theft, container escape, network-policy bypass, and cluster-admin escalation. No automatic execution, persistence, external exfiltration, or hardcoded secret is visible in the supplied portion. It should be restricted to authorized security testing and treated as sensitive content.
This fragment is highly dangerous offensive Kubernetes and cloud security guidance, including explicit backdoors, reverse shells, persistence, credential access, exfiltration, lateral movement, and detection evasion. It does not by itself show executable malware or npm supply-chain behavior; the primary risk is that users may copy and execute the commands. Review the surrounding package and publication context to determine whether these examples are intentionally included as security-training material or are accompanied by executable payloads.
This fragment is an offensive Kubernetes security-testing and attack-technique reference. It contains dangerous commands for privilege escalation, container escape, secret access, cloud-role assumption, and persistence, so it should only be used in explicitly authorized environments. However, the supplied portion contains no executable package code or automatic malicious behavior, and it does not by itself establish malware or a supply-chain backdoor.
This fragment is an offensive Kubernetes/container security playbook. It contains no visible autonomous malware or package-installation behavior, but it documents concrete techniques for host escape, credential and secret theft, privilege escalation, lateral movement, persistence, and detection evasion. Its misuse potential and security risk are high even though malware intent is not established from the supplied documentation alone.