What Happened
Cybersecurity researchers have uncovered two hijacked npm packages and a cluster of Go packages that are designed to deploy a Python-based information stealer on compromised Windows, Linux, and macOS hosts. "This attack avoids the most common npm execution paths through lifecycle scripts, perhaps in an attempt to remain 'compatible' with npm v12's security hardenings," JFrog said in a
Why It Matters
According to JFrog and The Hacker News, attackers hijacked two npm packages and at least 16 Go packages to deliver a Python-based infostealer across Windows, Linux, and macOS by abusing hidden VS Code tasks that auto-run when a project folder is opened.[1][3] The malware retrieves encrypted JavaScript from blockchain transaction data, establishes a socket.io backdoor, and then performs extensive credential and wallet harvesting from browsers, OS stores, developer tooling, and crypto applications.[1][2][3] From a CyberSE.AI perspective, this is a classic software supply chain compromise that directly affects developer environments—which are often used to build, test, and run AI systems—making it critical to maintain SBOMs, vet third-party packages, and harden IDE configurations. Organizations building or operating AI agents should treat developer workstations and their package ecosystems as part of the AI supply chain and implement continuous dependency monitoring, workspace trust policies, and credential hygiene to prevent infostealer-driven lateral movement into AI infrastructure.
CyberSE Analysis
This signal maps to AI supply chain. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.
Recommended Actions
- Restrict AI agent tool permissions and production write paths.
- Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
- Add human approval workflows for high-impact or state-changing actions.
- Run prompt injection and indirect prompt injection tests against affected workflows.
- Document the owner, control gap, and remediation deadline for this risk class.
Source
https://thehackernews.com/2026/06/hijacked-npm-and-go-packages-use-vs.html