Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bettermode-iconsnpm

Malicious code in bettermode-icons (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192938
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bettermode-icons

What this malware does

The package bettermode-icons was found to contain malicious code.

The OpenSSF Package Analysis project identified 'bettermode-icons' @ 999.1.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
999.1.0999.1.1

Indicators of compromise (SHA-256)

fc392f20a867c724f16f8b1e018f4789fc1a0e2bf878b64d1f752aa7188697cf
1ceadc93d3c27bfa5499a085742877e862d4e5a284ecb5cfdabd1a7e7b411c24
cea8112bbccd7b047a03169d6591f7ab7f756044a4203b2435152fe708cad5d5

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove bettermode-icons 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.

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks bettermode-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. bettermode-icons on npm has been identified as a malicious package (versions 999.1.0, 999.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks bettermode-icons-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.

bettermode-icons (npm) malicious package — MAL-2025-192938 | O3 Security