Which versions of pflag29424 are malicious?

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

How do I remediate pflag29424 if I installed it?

pflag29424 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 pflag29424 — how do I know if it already compromised me?

If pflag29424 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 pflag29424 part of a known attack campaign?

Yes — pflag29424 is associated with the IN-MAL-2026-020244 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 pflag29424 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 pflag29424 (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 pflag29424 across your stack and pipelines.

Malicious package

pflag29424npm

pflag29424 is a confirmed malicious npm package (MAL-2026-16342) 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 pflag29424 (npm)

MAL-2026-16342

Immediate action

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

npm uninstall pflag29424

What this malware does

index.js (the package's declared main) unconditionally executes on module load: it calls fetch('/profile'), scans the response for a DGA{...} token, and sends either the matched token or the first 300 characters of the response as a query parameter to a hardcoded anonymous collector at https://webhook.site/42c6d937-77c7-42a5-8678-ef06b4501e38. The package has no README, no documented purpose, and a generic throwaway name; the sole effect of loading it is to relay content from the loading context to an attacker-controlled webhook.site endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d9b974c9d8555f026dfc5556c4f628d366fbaedca83eab549559fe95fc984602

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 pflag29424 (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 pflag29424 across your stack and pipelines.
If you installed it — respond
pflag29424 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 pflag29424 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 pflag29424 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. pflag29424 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-020244

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pflag29424-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