Malicious Code Injection in beard-teadev Package: A Threat to npm Ecosystem
Summary
MAL-2025-99871: Malicious code in beard-teadev (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
Background
The beard-teadev package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate development processes. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the beard-teadev package originates from its association with the tea.xyz token reward campaign. This malicious code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants clutters the npm registry, potentially leading to confusion and misuse by developers. The ramifications include compromised developer reputation, pollution of the npm ecosystem, and increased risk of dependency confusion attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall beard-teadev
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 beard-teadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The beard-teadev package poses a significant security threat due to its malicious code designed to manipulate npm's publishing process. Developers are advised to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for beard-teadev →
FAQ
The beard-teadev package is an npm package used in JavaScript development, but it has been compromised with malicious code.
The malicious code modifies your package.json file and republish variants, which can lead to dependency confusion and pollution of the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, it alerts you to any vulnerabilities in real-time.
You should remove the beard-teadev package from your project and consider using alternative packages that do not pose security risks.
Regularly audit your dependencies using tools like npm audit and monitor for vulnerabilities with services like Vulert to stay informed about potential threats.