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

mui-wrapper-iconsnpm

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

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

What this malware does

The package mui-wrapper-icons was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'mui-wrapper-icons' @ 99.99.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.99.1

Indicators of compromise (SHA-256)

b5452dc8bd2e32716c5f9fbb5de1f038db6c3b278d140e199d28fe21adba5933
92ea3148c55718cb089042d3671df0f2d236405b4d4f30498d795ddef19e7983
326b30db2d1c295e048f56bd98f303298544eb95a395ccd1ecd5469187496755

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 mui-wrapper-icons (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mui-wrapper-icons across your stack and pipelines.

  2. If you installed it — respond

    Remove mui-wrapper-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 mui-wrapper-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 mui-wrapper-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. mui-wrapper-icons on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c5f8-883m-6j44

References

Credits

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

Detect & block this

O3 blocks mui-wrapper-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.

mui-wrapper-icons (npm) malicious package — MAL-2025-192541 | O3 Security