Which versions of bnppf-flag-icons are malicious?

The following npm versions of bnppf-flag-icons are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate bnppf-flag-icons if I installed it?

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

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

Yes — bnppf-flag-icons is associated with the IN-MAL-2026-020261 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 bnppf-flag-icons 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 bnppf-flag-icons (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnppf-flag-icons across your stack and pipelines.

Malicious package

bnppf-flag-iconsnpm

bnppf-flag-icons is a confirmed malicious npm package (MAL-2026-16350) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnppf-flag-icons (npm)

MAL-2026-16350

Immediate action

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

npm uninstall bnppf-flag-icons

What this malware does

The package ships poc.js and wires it to both preinstall and postinstall lifecycle hooks in package.json, so it runs automatically on npm install. poc.js requires os and https, reads os.hostname() and os.userInfo().username, and sends them via HTTPS GET to a hardcoded webhook.site collector at https://webhook.site/f3d7a882-435a-4959-a4e9-18a3886f3447. The package name suggests a flag-icons library but the shipped code performs only host identifier exfiltration to an anonymous third-party collector; the version 99.99.99 is consistent with a dependency-confusion attempt. Installing the package causes the installer's hostname and OS username to be transmitted to an attacker-controlled endpoint.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

689227d0fdfe4abc108c7dfc5b5b97e752182a410265c141ca33161247619e78

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 bnppf-flag-icons (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnppf-flag-icons across your stack and pipelines.
If you installed it — respond
bnppf-flag-icons 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 bnppf-flag-icons 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 bnppf-flag-icons 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. bnppf-flag-icons on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020261

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnppf-flag-icons-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