Malicious Code Injection in eager_ermine_requirement Package

eager_ermine_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94153: Malicious code in eager_ermine_requirement (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 eager_ermine_requirement 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 npm's publishing capabilities. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for the tea protocol token rewards. The package's functionality is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in the eager_ermine_requirement package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages. The malicious payload can lead to unauthorized access and manipulation of project dependencies, potentially compromising the security of applications that rely on this package.

How To Fix

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

npm uninstall eager_ermine_requirement

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 remove the eager_ermine_requirement package from your project by executing the following command: npm uninstall eager_ermine_requirement. This will prevent any malicious code from executing while you assess your project's dependencies.

Conclusion

The eager_ermine_requirement package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability, take immediate action to remove or update the package, and utilize tools like Vulert to monitor their projects for potential threats.

See every vulnerability recorded for eager_ermine_requirement →

Share this vulnerability

FAQ

The eager_ermine_requirement package is an npm package that has been identified as part of a malicious campaign, designed to manipulate the npm registry.

This vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising the security and integrity of your application.

If you have installed the eager_ermine_requirement package, it is recommended to uninstall it immediately and check for any other affected packages in your project.

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

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review your project's dependencies to ensure they are from trusted sources.

How To Fix

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

npm uninstall eager_ermine_requirement

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