k8s-network-recon

Fail

Audited by Snyk on May 4, 2026

Risk Level: CRITICAL
Full Analysis

CRITICAL E006: Malicious code pattern detected in skill scripts.

  • Malicious code pattern detected (high risk: 1.00). This skill is explicitly malicious: it provides step-by-step offensive techniques for Kubernetes reconnaissance and exploitation (DNS PTR/SRV/AXFR enumeration, ARP and DNS spoofing, CoreDNS ConfigMap poisoning, MITM traffic interception, credential harvesting, hostNetwork abuse and scanning/exploitation of management services), clearly enabling unauthorized lateral movement, credential/data exfiltration, and potential cluster takeover.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 0.90). The skill's required workflow (Phase 3 "访问发现的服务" with commands like "curl ..." and the use of K8Spider/k8spider installation via "go install github.com/Esonhugh/k8spider@latest") explicitly fetches and interprets responses from discovered/untrusted services and public repos, so third-party content could materially influence subsequent actions.

Issues (2)

E006
CRITICAL

Malicious code pattern detected in skill scripts.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

Audit Metadata
Risk Level
CRITICAL
Analyzed
May 4, 2026, 08:16 AM
Issues
2
Security Audit — snyk — k8s-network-recon