Loading story…
vlt technology inc. released vlt 1.0, a JavaScript package manager and hosted registry designed as a drop-in replacement for npm. The release provides ecosystem mirrors and a phased installation process that separates package download from lifecycle-script execution; scripts run only during an explicit build step, reducing exposure to malicious install-time behavior.
The platform integrates Socket-powered, real-time dependency-graph analysis and security selectors, and its registries block known-malicious packages before they are served. vlt says it has identified more than 275,000 suspicious or malicious package versions, including versions it reports remain available through npm, positioning the service as a supply-chain security control for JavaScript development environments.
Trace attribution and downstream blast radius.
2 events from the most recent confirmed update back to the earliest known activity.
vlt technology inc. released vlt 1.0, a drop-in npm replacement with hosted registries and ecosystem mirrors. The release separates package download from lifecycle-script execution, blocks known-malicious packages by default during builds, and adds Socket-powered dependency-graph security queries.
vlt launched real-time dependency analysis powered by Socket, as identified in the Socket announcement title.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researchers reported an npm supply-chain compromise involving a malicious package, `polymarket-clob`, that targeted cryptocurrency users by exfiltrating sensitive local files (including `.env`, `wallets.json`, and `keys/*.json`) to attacker-controlled infrastructure. The package was published in the npm registry, downloaded at least 189 times (lower bound), and later removed and replaced with a security placeholder; analysis of the code and infrastructure pivoting linked the campaign to broader activity consistent with wallet-drainer operations and **Vidar** stealer-related infrastructure, including reuse of SSH fingerprints and consistent hosting patterns. Separately, researchers disclosed **six JavaScript “zero-day” bypass issues** across multiple package managers—**npm, pnpm, vlt, and Bun**—that undermine common defensive controls used to reduce supply-chain risk, including disabling lifecycle scripts and relying on lockfile integrity. The issues (dubbed **“PackageGate”**) reportedly enable paths to regain install-time code execution or weaken integrity guarantees via mechanisms such as Git dependency handling, tar extraction behaviors, and incomplete integrity coverage for URL-based tarballs; pnpm, vlt, and Bun were reported as patched, while npm characterized the behavior as “works as expected,” raising concern that package-manager-level weaknesses could enable large-scale compromise even in hardened environments.
Jun 29, 2026
Researchers reported that the npm package **`shai_hulululud@1.0.48596`** was built to interfere with **AI-assisted malware analysis** rather than to execute a conventional JavaScript payload. The package’s **9.28 MB** `index.js` file embeds policy-triggering text, fake system instructions, a large Japanese-language comment block, and tens of thousands of repetitive comment lines intended to cause LLM refusals, truncation, timeouts, or misclassification before analysts or automated tools reach the executable code. Reports said the file can expand to more than **3.5 million tokens**, while the actual logic is hidden later in an obfuscated `try{eval(...)} ` wrapper using character-code arrays and substitution routines. Socket assessed the package as **protestware or a potentially unwanted adversarial test case**, not the same credential-stealing malware seen in earlier **Mini Shai-Hulud, Miasma, and Hades** npm campaigns, but warned that the technique could be adopted by more capable threat actors. Coverage of the package highlighted that the malicious or suspicious content sits inside comments and is therefore aimed at **LLM-first review pipelines**, while traditional methods such as static analysis, AST parsing, string extraction, deobfuscation, entropy checks, YARA, and behavioral rules remain effective. Recommended defenses include stripping comments before model analysis, detecting context flooding, prioritizing executable code paths, combining LLM review with conventional scanning, and **failing closed** when AI systems refuse, time out, or return incomplete results.
Jun 29, 2026
A software supply chain compromise hit the JavaScript ecosystem after malicious versions of **Keyv** and related npm packages were published through legitimate maintainer workflows, with `keyv@6.0.0` identified as a primary malicious release. Researchers said the tainted packages added a `preinstall` hook that executed attacker code during dependency installation on developer workstations and CI runners, while some repositories also contained malicious **VS Code** and **Claude Code** configuration files that could trigger execution when a cloned project was opened. Early community reports tied the incident to the `jaredwray/cacheable` package set and warned that numerous downstream dependencies were exposed. Analysis found the malware targeted high-value secrets including **GitHub** and **npm** tokens, cloud credentials, Vault tokens, Kubernetes service account tokens, SSH keys, and TLS certificates, with tradecraft resembling the **Shai-Hulud** malware family. Investigators reported no evidence that npm itself was breached; instead, the attackers appear to have used stolen maintainer credentials and trusted GitHub Actions publishing pipelines with valid provenance and npm attestation, demonstrating that provenance verified the build source but not whether the source had already been maliciously altered. Responders were urged to avoid affected versions, isolate any host that installed them, remove persistence such as `gh-token-monitor`, and rotate exposed credentials from a clean system.
Aug 8, 2026