fb-insurance--boxified-form-vzr-testnpm
fb-insurance--boxified-form-vzr-test is a confirmed malicious npm package (MAL-2026-12179) that executes malicious code on install (malicious version 20.3.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fb-insurance--boxified-form-vzr-test (npm)
What this malware does
On require of the package, index.js loads _loader.js which selects a platform-specific endpoint, fetches an executable payload over HTTPS from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, cf100-416.workers.dev, cf103-070.workers.dev), writes it to /var/tmp or %TEMP% under a deceptive filename (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached-and-unref'd via /bin/sh -c or cmd. If the HTTPS mirrors fail, _loader.js falls back to a DNS-TXT covert channel: it resolves c.<domain> for a chunk count against resolvers under *.dl.well1.site (tin/tina/ldr/win subdomains) and reassembles N base64 TXT fragments from <i>.<domain> into the same executable buffer. Destination hostnames and resolver domains are constructed at runtime by joining short substring arrays (e.g. ['oob-worker.cf99-9b3','.worker','s.dev'].join('')) to evade static string matching. No hash or signature is verified on the fetched bytes. The fetched executable runs with the installer's privileges.
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 fb-insurance--boxified-form-vzr-test (version 20.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fb-insurance--boxified-form-vzr-test across your stack and pipelines.
If you installed it — respond
Remove fb-insurance--boxified-form-vzr-test 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 fb-insurance--boxified-form-vzr-test 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 fb-insurance--boxified-form-vzr-test 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 fb-insurance--boxified-form-vzr-test-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.