Which versions of pflag14570 are malicious?

The following npm versions of pflag14570 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pflag14570 if I installed it?

pflag14570 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.

I already installed pflag14570 — how do I know if it already compromised me?

If pflag14570 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.

Is pflag14570 part of a known attack campaign?

Yes — pflag14570 is associated with the IN-MAL-2026-020245 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find pflag14570 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pflag14570 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pflag14570 across your stack and pipelines.

Malicious package

pflag14570npm

pflag14570 is a confirmed malicious npm package (MAL-2026-16341) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pflag14570 (npm)

MAL-2026-16341

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall pflag14570

What this malware does

index.js is an IIFE that executes at module load, reads document.cookie, fetches a list of authenticated application paths (/profile, /admin, /api/me, /settings, and similar), extracts a flag-shaped substring from the responses, and POSTs the aggregated JSON to the hardcoded collector https://webhook.site/42c6d937-77c7-42a5-8678-ef06b4501e38. The package metadata is a stub with no legitimate documented function; the shipped body is a browser-context session-cookie stealer and endpoint scraper directed at a third-party attacker-controlled collector.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2b7164c1405ab2587c562b3b9eb8cdad8258aab8f25b829da64c83d7185eab6c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pflag14570 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pflag14570 across your stack and pipelines.
If you installed it — respond
pflag14570 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 pflag14570 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 pflag14570 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

No. pflag14570 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020245

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pflag14570-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database