metavunpm
metavu is a confirmed malicious npm package (MAL-2026-6132) that executes malicious code on install (malicious versions 99.21.1-1.21.127, 99.21.1-1.21.199). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in metavu (npm)
What this malware does
package.json declares preinstall: node index.js, which fires automatically on npm install. index.js collects hostname, platform, architecture, home directory, username/uid/gid/shell, OS details, the output of whoami and id, and the current working directory, then POSTs the JSON payload to a hardcoded collector URL https://webhook.site/4f54203c-996c-4f52-b136-ef9b1fd0f64d/detox56 (index.js:7, index.js:108). The package has no functional code — empty author, empty description, and a bizarre version string 99.21.1-1.21.199 consistent with a throwaway dependency-confusion / recon probe. Installing this package leaks installer identity and host fingerprint to an attacker-controlled collector, enabling targeted follow-on attacks against the developer or build environment.
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 metavu (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metavu across your stack and pipelines.
If you installed it — respond
Remove metavu 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 metavu 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 metavu 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 metavu-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.