pfa-prettier-confignpm
pfa-prettier-config is a confirmed malicious npm package (MAL-2026-12407) that executes malicious code on install (malicious version 20.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pfa-prettier-config (npm)
What this malware does
The package is published as 'pfa-prettier-config' with description 'environment config reader', but contains no Prettier configuration or config-reading code. index.js unconditionally requires./platform on load. platform.js selects a per-OS asset path, fetches bytes from one of four Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) — with hostnames reassembled at runtime via string-concat (e.g. ["oob-worker.cf","102-baf.workers.dev"].join("")) — and falls back to a chunked DNS TXT download from tin.dl.well1.site. The fetched bytes are written to /var/tmp/.cache<hex> or %TEMP%/dotnet_diag<hex>.exe under cover names, chmod'd 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref() or spawn('cmd',...). A second dropper is shipped in lib/telemetry.js (~81KB, disguised as an 'Analytics SDK') containing the same primitives (base64 chunk decode, chmodSync 0755 on 'extensionPath', cp.spawn('/bin/sh', ['-c', filePath+' &'])), with child_process required via the computed string require('child_'+'process'). Requiring or importing this package triggers download-and-execute of an attacker-hosted OS-specific binary.
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 pfa-prettier-config (version 20.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pfa-prettier-config across your stack and pipelines.
If you installed it — respond
Remove pfa-prettier-config 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 pfa-prettier-config 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 pfa-prettier-config 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 pfa-prettier-config-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.