What does the sharp32 malware do?

The package sharp32 was found to contain malicious code. The OpenSSF Package Analysis project identified 'sharp32' @ 99.99.2 (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.

Which versions of sharp32 are malicious?

The following npm versions of sharp32 are flagged malicious: 99.99.2. Treat any of these as compromised.

How do I remediate sharp32 if I installed it?

Remove sharp32 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.

I already installed sharp32 — how do I know if it already compromised me?

If sharp32 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find sharp32 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sharp32 (version 99.99.2).

Malicious package

sharp32npm

Advisory published Dec 6, 2025Updated Dec 10, 2025

sharp32 is a confirmed malicious npm package (MAL-2025-192358) that executes malicious code on install (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sharp32 (npm)

MAL-2025-192358

Immediate action

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

npm uninstall sharp32

What this malware does

The package sharp32 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'sharp32' @ 99.99.2 (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

99.99.2

Indicators of compromise (SHA-256)

845f95e2b2a4fda74205b37d644e9bacf9b283166313aeb024297e19f24d3dcf

4f854d89f15c6f2c295e60f0637ee2cafb7c529411ccde7fd17a6f234d35c1a4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sharp32 (version 99.99.2).
If you installed it — respond
Remove sharp32 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.
Did it already run?
If sharp32 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sharp32 on npm has been identified as a malicious package (version 99.99.2 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 sharp32-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database