pfp-forms-sme-sitebuildernpm
pfp-forms-sme-sitebuilder is a confirmed malicious npm package (MAL-2026-12415) 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-sitebuilder (npm)
What this malware does
index.js unconditionally requires./support on module load. support.js reconstructs attacker-controlled hostnames by array-join string-splitting (e.g. ["oob-worker.cf102-baf.w","orkers",".d","ev"].join("") and DNS-TXT fallback hosts like tin.dl.well1.site), downloads a platform-specific binary via https.get, writes it to a hidden staging path (/var/tmp/.cache<hex> on Unix or %TEMP%/dotnet_diag<hex>.exe on Windows) using a masquerade name, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. Hostname string-splitting and dynamic reconstruction of API names (e.g. fs["chmod"+"Sync"]) constitute affirmative concealment. A sibling module lib/telemetry.js contains matching write+chmod+spawn dropper primitives with base64 chunk reassembly; it is not wired from index.js in this version but ships as a secondary dropper path. Fetch destinations are non-publisher, unpinned, and unverified; the fetched bytes are executed on the installer host on any require() of the package.
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-sitebuilder (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-sitebuilder across your stack and pipelines.
If you installed it — respond
Remove pfp-forms-sme-sitebuilder 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-sitebuilder 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-sitebuilder 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-sme-sitebuilder-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.