Malicious Code Detected in sharp32 Package - Version 99.99.2

sharp32 Updated 06 Dec 2025

Summary

06/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192358: Malicious code in sharp32 (npm). Affects sharp32 versions 99.99.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sharp32 package is a Node.js library designed for image processing, allowing developers to resize, crop, and manipulate images efficiently. It is widely used in web applications for handling image uploads and transformations. However, the specific version 99.99.2 has been flagged for containing malicious code that compromises the security of applications utilizing it.

Vulnerability Detail

The vulnerability in sharp32 arises from its communication with a domain linked to malicious activities and the execution of commands that can lead to harmful behavior. This can result in unauthorized access to sensitive data, potential data breaches, and the execution of arbitrary code within the user's environment. The origin of this vulnerability has been traced back to the OpenSSF Package Analysis project, which identified the malicious nature of this package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall sharp32

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, consider removing the sharp32 package from your project until a secure version is released. You can do this by running the command: npm uninstall sharp32. Alternatively, you can explore other image processing libraries that do not have known vulnerabilities.

Conclusion

The sharp32 package version 99.99.2 has been flagged for containing malicious code that poses significant security risks. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for sharp32 →

Share this vulnerability

FAQ

sharp32 is a Node.js library used for image processing, allowing developers to manipulate images efficiently.

Version 99.99.2 of sharp32 is identified as malicious and should be avoided.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using the affected version can lead to unauthorized access, data breaches, and execution of harmful commands within your application.

Yes, you can temporarily uninstall the sharp32 package or switch to alternative libraries until a secure version is available.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall sharp32

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback