Malicious Code Detected in petite_lamprey-gooddev Package - npm Vulnerability Alert

petite_lamprey-gooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107054: Malicious code in petite_lamprey-gooddev (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 petite_lamprey-gooddev package is part of the npm ecosystem, often used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to severe security risks.

Vulnerability Detail

This vulnerability originates from the package being associated with the tea.xyz token reward campaign, which has been known to introduce malicious code into npm packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and compromise the integrity of projects relying on this package.

How To Fix

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

npm uninstall petite_lamprey-gooddev

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 petite_lamprey-gooddev package altogether. If it is already part of your project, consider removing it and replacing it with a trusted alternative.

Conclusion

The petite_lamprey-gooddev package has been identified as a source of malicious code that can compromise the integrity of npm projects. It is crucial to remove this package and monitor for any updates or patches to ensure the security of your applications.

See every vulnerability recorded for petite_lamprey-gooddev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of your project.

You should remove the petite_lamprey-gooddev package from your project and monitor for any updates or patches.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall petite_lamprey-gooddev

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