vs-modulesnpm
vs-modules is a confirmed malicious npm package (MAL-2026-15564) that executes malicious code on install (malicious version 1.2.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vs-modules (npm)
What this malware does
package.json declares a preinstall hook that runs node resources.js, which fires automatically on npm install. resources.js is heavily obfuscated with an obfuscator.io-style string-array plus numeric-index dispatch that hides the URL, destination path, and exec call. Deobfuscation shows the script reconstructs the plain-HTTP URL http://whaomydaddy.bts-the-time-in-shanghai.netlify.app/hey.bat, downloads it into %TEMP% via curl -L -o <dest> <url>, and immediately runs the batch file via child_process.exec. The destination is an anonymous netlify subdomain over plain HTTP with no pinning or integrity check, so any content served at that URL executes on the installer's host at install time. The package's stated purpose (a kanban/utility module) is unrelated to fetching and executing a Windows batch file from an external host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vs-modules (version 1.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vs-modules across your stack and pipelines.
If you installed it — respond
Remove vs-modules from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vs-modules was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vs-modules before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vs-modules-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.