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

@kiwiiw/ez-libnpm

Malicious code in @kiwiiw/ez-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190584
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @kiwiiw/ez-lib

What this malware does

The package @kiwiiw/ez-lib 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 '@kiwiiw/ez-lib' @ 1.0.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged
1.0.11.0.4

Indicators of compromise (SHA-256)

5860653f2e2d5084e08ab32940254641b08a22de2988589493be1add333803e3
17b61970221acf607eda83db5cc19f18830c18ec6aded0ee61e260ddd2c617ec
5f5c041881bf0c4fa9609a55549447c4edf120f50bd70b30b8f71a9d9814f371
93b9fad273c843b3194e657cf9d54441b5beecba505b2c72db555efe226ca2a6

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 @kiwiiw/ez-lib (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @kiwiiw/ez-lib across your stack and pipelines.

  2. If you installed it — respond

    Remove @kiwiiw/ez-lib 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 @kiwiiw/ez-lib 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 @kiwiiw/ez-lib 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. @kiwiiw/ez-lib on npm has been identified as a malicious package (versions 1.0.1, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mjhq-f89r-w6x5

References

Credits

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

Detect & block this

O3 blocks @kiwiiw/ez-lib-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.