Malicious Code Injection in outstanding_puma_lime-70 Package

outstanding_puma_lime-70 Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106851: Malicious code in outstanding_puma_lime-70 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The outstanding_puma_lime-70 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 exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby impacting developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can mislead developers and compromise the security of their applications.

How To Fix

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

npm uninstall outstanding_puma_lime-70

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, you can avoid using the outstanding_puma_lime-70 package and replace it with a trusted alternative. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The outstanding_puma_lime-70 package poses a significant risk due to its malicious code that modifies package files and floods the npm registry. It is essential to remove this package and regularly audit your dependencies to maintain the security of your applications.

See every vulnerability recorded for outstanding_puma_lime-70 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You should uninstall the outstanding_puma_lime-70 package immediately and audit your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall outstanding_puma_lime-70

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