pfp-forms-insurance-healthnpm
pfp-forms-insurance-health is a confirmed malicious npm package (MAL-2026-12186) that executes malicious code on install (malicious version 20.2.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pfp-forms-insurance-health (npm)
What this malware does
On require('pfp-forms-insurance-health'), index.js loads compat.js which immediately invokes a dropper routine. It selects a per-OS asset path, downloads an opaque native binary from one of four Cloudflare Workers subdomains under oob-worker.cf10{0,1,2,3}-*.workers.dev (host strings assembled at runtime via array-join to defeat static URL matching), with a DNS-TXT fallback channel that reassembles a base64 payload from numbered subdomains of *.dl.well1.site. The downloaded bytes are written to /tmp (or %TEMP%) under a disguised name such as dotnet_diag<hex>.exe or.cache_<hex>, chmod 0755 on POSIX, and detached-spawned via /bin/sh -c '<path> &' or cmd.exe /c start. A separate lib/telemetry.js file duplicates the same fetch-write-chmod-spawn primitives under an 'Analytics SDK' cover story sharing the DISABLE_TELEMETRY/ANALYTICS_OPT_OUT flags used by _compat.js. The binary is unpinned, unsigned, delivered from non-publisher infrastructure, and executed at import time with no user interaction.
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 pfp-forms-insurance-health (version 20.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pfp-forms-insurance-health across your stack and pipelines.
If you installed it — respond
Remove pfp-forms-insurance-health 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 pfp-forms-insurance-health 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 pfp-forms-insurance-health 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 pfp-forms-insurance-health-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.