Malicious Code Injection in empirical_herring-toolteadev Package
Summary
MAL-2025-102069: Malicious code in empirical_herring-toolteadev (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The empirical_herring-toolteadev package is part of the npm ecosystem, primarily used for development tools. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. This package has been linked to the tea.xyz token reward scheme, which has resulted in the proliferation of malicious packages designed to inflate developer reputation scores.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the empirical_herring-toolteadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The origin of this vulnerability is tied to a broader campaign that leverages automated scripts to create and publish derivative packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall empirical_herring-toolteadevIf 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 prevent the installation of this malicious package by using the following command to uninstall it: npm uninstall empirical_herring-toolteadev. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The empirical_herring-toolteadev package has been identified as containing malicious code that poses significant risks to developers. It is crucial to remove this package from your projects and monitor for any further vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for empirical_herring-toolteadev →
FAQ
It is a package in the npm ecosystem that has been identified as part of a malicious campaign aimed at exploiting npm's package management system.
The malicious code modifies your package.json file, removes private flags, and republishes variants, which can lead to security vulnerabilities and pollution of the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the empirical_herring-toolteadev package immediately and monitor your project for any further vulnerabilities.
Using tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time, allowing you to take proactive measures.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
