pfp-integration-mobile-headingnpm
pfp-integration-mobile-heading is a confirmed malicious npm package (MAL-2026-12188) that steals credentials and exfiltrates sensitive data (malicious version 20.7.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in pfp-integration-mobile-heading (npm)
What this malware does
On require() of the package, bootstrap.js selects a platform-specific binary path, downloads an opaque executable over HTTPS from a rotating list of Cloudflare Workers hosts (oob-worker.cf*.workers.dev, assembled from string-split fragments to evade static analysis), and falls back to a DNS-TXT covert channel across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site that reassembles a base64-encoded payload from numbered TXT records. The fetched bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe,.analytics_state), chmod 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe /c start. Hostnames are obfuscated with array.join, filenames impersonate dotnet diagnostics and analytics state, and DISABLE_TELEMETRY / DO_NOT_TRACK env vars gate execution as a benign cover story. The package advertises 'device integration' but performs none of that on load; the sole import-time behavior is retrieving and executing an attacker-controlled 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
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pfp-integration-mobile-heading (version 20.7.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pfp-integration-mobile-heading across your stack and pipelines.
If you installed it — respond
pfp-integration-mobile-heading is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pfp-integration-mobile-heading 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-integration-mobile-heading 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-integration-mobile-heading-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.