Malicious Code Injection in dariobaguette: A Threat to npm Users
Summary
MAL-2025-171088: Malicious code in dariobaguette (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
dariobaguette is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in dariobaguette originates from its association with a malicious campaign that floods the npm registry with fake packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, leading to potential security breaches and loss of developer credibility.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dariobaguetteIf 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 measure, you can avoid using the dariobaguette package and instead rely on alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit.
Conclusion
The discovery of malicious code in the dariobaguette package highlights the importance of vigilance when using open-source software. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their projects and maintain the integrity of their software dependencies.
See every vulnerability recorded for dariobaguette →
FAQ
The main risk is the potential for malicious code execution and the pollution of the npm registry with fake packages, which can lead to security vulnerabilities in dependent projects.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts for vulnerabilities.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and monitor for updates and security advisories from package maintainers.
If you have installed the dariobaguette package, it is advisable to remove it immediately and check your project for any dependencies that may have been affected.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.
