Malicious Code Injection in reluctant_hamster-gooddev Package

reluctant_hamster-gooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107873: Malicious code in reluctant_hamster-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The reluctant_hamster-gooddev package is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. The malicious behavior includes modifying essential files and continuously republishing variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a larger malicious scheme associated with the tea.xyz token reward campaign. It contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall reluctant_hamster-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 reluctant_hamster-gooddev package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The reluctant_hamster-gooddev package is a malicious npm package that poses significant risks to developers and the integrity of the npm registry. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain a secure development environment.

See every vulnerability recorded for reluctant_hamster-gooddev →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that automates the generation of derivative packages for token rewards.

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

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

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality while ensuring they are reputable and secure.

How To Fix

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

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