Malicious Code Injection in charusharma Package: npm Vulnerability Alert

charusharma Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171032: Malicious code in charusharma (npm). Affected versions are not published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The charusharma package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns for developers who may unknowingly incorporate it into their projects.

Vulnerability Detail

The vulnerability in the charusharma package originates from its association with a malicious token reward campaign that floods the npm registry. The package contains scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. This malicious behavior includes modifying the package.json file to remove private flags, altering version numbers, and continuously republishing variants, which can lead to reputation inflation for the perpetrators and potential security risks for users of the package.

How To Fix

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

npm uninstall charusharma

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 measure, avoid using the charusharma package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.

Conclusion

The charusharma package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor their projects for potential threats.

See every vulnerability recorded for charusharma →

Share this vulnerability

FAQ

The charusharma package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If your project uses the charusharma package, it may be at risk of being affected by malicious code that can compromise your application's integrity and security.

You should uninstall the charusharma package immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall charusharma

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