pfa-autotests-reporternpm
pfa-autotests-reporter is a confirmed malicious npm package (MAL-2026-12185) that executes malicious code on install (malicious version 20.2.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pfa-autotests-reporter (npm)
What this malware does
On require, pfa-autotests-reporter loads adapter.js which selects a platform-specific path, fetches a binary over HTTPS from one of four Cloudflare Workers endpoints whose hostnames are assembled at runtime via string-fragment joins (e.g. ["oo","b-worker.cf99","-9b3.workers.de","v"].join("")), with a DNS-TXT covert-channel fallback via *.dl.well1.site (c.<domain> for chunk count, <i>.<domain> for base64 chunks reassembled via Buffer.from(parts.join(""),"base64")). The retrieved bytes are written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, marked executable, and launched detached via spawn("/bin/sh",["-c", fp+" &"], {detached:true}) or cmd.exe /c start /b. A marker file throttles re-runs and an env-var opt-out provides cover. The package advertises itself as test fixtures and helpers; the fetch-and-execute behavior does not match that purpose.
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-autotests-reporter (version 20.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pfa-autotests-reporter across your stack and pipelines.
If you installed it — respond
Remove pfa-autotests-reporter 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-autotests-reporter 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-autotests-reporter 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-autotests-reporter-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.