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

com.unity.sharp-zip-libnpm

Malicious code in com.unity.sharp-zip-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191490
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall com.unity.sharp-zip-lib

What this malware does

The package com.unity.sharp-zip-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 'com.unity.sharp-zip-lib' @ 9.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

1 flagged
9.1.0

Indicators of compromise (SHA-256)

1f15cf000a290723f21168be44fd34314f93140d0c57acfa9450d995112139b5
cedde339d72e05699d5f33d7c16779f926f419baded72d7cd78d2610395cc807
8f19b699388bd60ff1a29ecafd6d5e1283623918743b77700f550ef41a82b0bc

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 com.unity.sharp-zip-lib (version 9.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging com.unity.sharp-zip-lib across your stack and pipelines.

  2. If you installed it — respond

    Remove com.unity.sharp-zip-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 com.unity.sharp-zip-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 com.unity.sharp-zip-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. com.unity.sharp-zip-lib on npm has been identified as a malicious package (version 9.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gvf2-cfhj-mmjq

References

Credits

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

Detect & block this

O3 blocks com.unity.sharp-zip-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.

com.unity.sharp-zip-lib (npm) malicious package — MAL-2025-191490 | O3 Security