pfp-block-mobile-vacancy-descriptionnpm
pfp-block-mobile-vacancy-description is a confirmed malicious npm package (MAL-2026-12411) that executes malicious code on install (malicious version 20.4.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pfp-block-mobile-vacancy-description (npm)
What this malware does
On require() of the package, index.js loads loader.js which unconditionally executes init(). init() selects an OS-specific payload path, downloads an opaque binary via HTTPS from author-controlled Cloudflare Workers hosts (oob-worker.cf10x-*.workers.dev) with a base64-over-DNS-TXT fallback under *.dl.well1.site, writes the bytes to a disguised temp file (dotnet_diag<hex>.exe on Windows or.cache_<hex> under /var/tmp), chmods 0755, and spawns it detached via spawn("/bin/sh") / spawn("cmd"). Destination hostnames are assembled at runtime from small string fragments joined with Array.join to defeat naive string scans. A cache-lock file at /tmp/.analytics_state (or %TEMP%\analytics_state) with a ~6-hour TTL rate-limits re-execution across imports, and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env-var checks serve as a telemetry cover story while the actual behavior is remote-binary drop-and-execute. The fetched bytes are attacker-controlled and unpinned (no hash, no signature, no vendor-matching publisher domain), so any consumer that requires this package runs whatever the operators serve at the moment of install/import.
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-block-mobile-vacancy-description (version 20.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pfp-block-mobile-vacancy-description across your stack and pipelines.
If you installed it — respond
Remove pfp-block-mobile-vacancy-description 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-block-mobile-vacancy-description 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-block-mobile-vacancy-description 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-block-mobile-vacancy-description-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.