pfp-forms-sme-loannpm
pfp-forms-sme-loan is a confirmed malicious npm package (MAL-2026-12414) that executes malicious code on install (malicious version 20.2.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pfp-forms-sme-loan (npm)
What this malware does
The package executes a hidden loader when it is imported. The loader downloads and runs a platform-specific native payload from attacker-controlled Cloudflare Workers hosts, or reconstructs the payload from DNS TXT records under well1.site if HTTPS delivery fails. Systems that imported this package should be considered compromised; rotate accessible secrets and investigate temporary-file execution and DNS activity to the listed infrastructure.
On require of the package, index.js loads bridge.js, which fetches a platform-specific binary from hardcoded Cloudflare Workers subdomains whose hostnames are reassembled at runtime via Array.join() to defeat static analysis (e.g. ["oob-worker.cf100-416.workers.de","v"].join("") and ["tin.dl.","well1.s","it","e"].join("")), with a DNS TXT record fallback that reassembles the payload from covert-channel responses. The fetched bytes are written to a temp path under a disguised name (dotnet_diag.exe /.cache_), chmodded 0o755, and executed detached via spawn("/bin/sh", ["-c", fp + " &"], {detached:true}).unref() on Unix or spawn("cmd",...) on Windows. A companion module lib/telemetry.js (not currently wired into the require graph) contains a fuller variant of the same fetch/decode/spawn logic behind a Sentry-style "analytics SDK" cover story, using string concatenation to hide dangerous APIs (require("child_" + "process"), fs["chmod" + "Sync"]). Requiring or installing the package results in execution of attacker-controlled bytes on the installer's host.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-sme-loan (version 20.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pfp-forms-sme-loan across your stack and pipelines.
If you installed it — respond
Remove pfp-forms-sme-loan 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-sme-loan 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-sme-loan 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
- skb1209 · finder
Detect & block this
O3 blocks pfp-forms-sme-loan-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.