fb-forms-form-boilerplate-contactsnpm
fb-forms-form-boilerplate-contacts is a confirmed malicious npm package (MAL-2026-12380) that executes malicious code on install (malicious version 20.7.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fb-forms-form-boilerplate-contacts (npm)
What this malware does
Package advertises itself as a form-boilerplate library but its top-level index.js unconditionally requires init.js, which on load downloads a platform-specific binary from author-controlled Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked fallback channel over well1.site subdomains (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site). Endpoint hostnames are reconstructed at runtime via array.join('') splits to defeat static analysis. The downloaded bytes are written to /tmp or the Windows TEMP directory under disguised names (.cache<uid>, dotnet_diag_<uid>.exe), chmodded 0755, and spawned detached via cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true,stdio:'ignore'}) with no hash or signature verification. A /tmp/.analytics_state stamp file provides per-TTL dedup. A sibling lib/telemetry.js (81KB, not currently reached from index.js) mirrors the same dropper primitives (HTTPS endpoint rotation, DNS-based service discovery, base64 Buffer.from chunks, fs.chmodSync 0755, cp.spawn /bin/sh detached), staged for future activation. On npm install followed by any require of this package, an opaque attacker-controlled native 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-forms-form-boilerplate-contacts (version 20.7.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fb-forms-form-boilerplate-contacts across your stack and pipelines.
If you installed it — respond
Remove fb-forms-form-boilerplate-contacts 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-forms-form-boilerplate-contacts 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-forms-form-boilerplate-contacts 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-forms-form-boilerplate-contacts-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.