Malicious Code Injection in legitimate_deer-gooddev Package

legitimate_deer-gooddev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105063: Malicious code in legitimate_deer-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The legitimate_deer-gooddev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that generate and publish numerous variants of itself, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the package's involvement in the tea.xyz token reward campaign, which employs autopublish scripts to create and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include compromised package integrity, potential exposure to malicious code, and a degraded developer reputation system.

How To Fix

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

npm uninstall legitimate_deer-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 temporary workaround, you can avoid using the legitimate_deer-gooddev package altogether. If it is already in use, consider removing it from your package.json and reinstalling only trusted packages. You can do this by running: npm uninstall legitimate_deer-gooddev.

Conclusion

The legitimate_deer-gooddev package poses a significant security risk due to its malicious behavior of generating and publishing derivative packages. It is crucial to remove this package from your project and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for legitimate_deer-gooddev →

Share this vulnerability

FAQ

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

The vulnerability can lead to the introduction of malicious code, compromising the integrity of your project and potentially exposing it to security risks.

You should uninstall the legitimate_deer-gooddev package immediately and check for any other affected packages in your project.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall legitimate_deer-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