Malicious Code Injection in waffle-notthedevs Package
Summary
MAL-2025-110647: Malicious code in waffle-notthedevs (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 waffle-notthedevs package is part of the npm ecosystem, primarily used for various development purposes. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package, like others in this campaign, contains scripts that automatically generate and publish derivative packages with randomized names, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in the waffle-notthedevs package originates from its association with the tea.xyz token reward campaign. It includes malicious payloads that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall waffle-notthedevsIf 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 waffle-notthedevs package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The waffle-notthedevs package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to update to a patched version or find alternatives to mitigate these risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for waffle-notthedevs →
FAQ
The vulnerability involves malicious code that modifies package.json and generates random package names, contributing to npm registry pollution.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using the affected package may lead to the installation of unwanted and potentially harmful packages, compromising your application's security and integrity.
Regularly updating your dependencies and using tools like Vulert to monitor vulnerabilities can help prevent similar issues.
If an immediate update is not possible, consider removing the package and using alternatives until a secure version is available.
