Malicious Code Injection in viper_lime-59: A Threat to npm Ecosystem

viper_lime-59 Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98496: Malicious code in viper_lime-59 (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

viper_lime-59 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package poses significant risks to developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in viper_lime-59 originates from its involvement in the tea.xyz token reward campaign, which 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. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their applications.

How To Fix

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

npm uninstall viper_lime-59

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 viper_lime-59 package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The viper_lime-59 package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for viper_lime-59 →

Share this vulnerability

FAQ

viper_lime-59 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising your application's security.

You should remove the viper_lime-59 package from your project and check for any updates or patches that address this vulnerability.

You can use tools like npm audit to regularly check for vulnerabilities in your project's dependencies.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall viper_lime-59

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