Malicious Code Vulnerability in garimaprasad Package

garimaprasad Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171257: Malicious code in garimaprasad (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The garimaprasad package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and can lead to significant security risks for developers using it.

Vulnerability Detail

The vulnerability in the garimaprasad package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to trust the integrity of packages. This poses a risk of unintentional use of compromised packages, leading to potential security breaches.

How To Fix

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

npm uninstall garimaprasad

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 workaround, you can avoid using the garimaprasad package and check for any dependencies that might be using it. You can also use the following command to uninstall the package: npm uninstall garimaprasad.

Conclusion

The garimaprasad package poses a significant security risk due to its malicious code designed to manipulate package data and pollute the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for garimaprasad →

Share this vulnerability

FAQ

The garimaprasad package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

Using the garimaprasad package can compromise the integrity of your project by introducing malicious code that modifies package settings and republishing variants.

If you have installed the garimaprasad package, it is recommended to uninstall it immediately and check for any dependencies that may rely on it.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall garimaprasad

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