Malicious Code Injection in wawan-kue70-breki: A Threat to npm Packages
Summary
MAL-2025-76177: Malicious code in wawan-kue70-breki (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 package 'wawan-kue70-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign that has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and developers alike.
Vulnerability Detail
The vulnerability in 'wawan-kue70-breki' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to compromised developer accounts and a polluted package ecosystem, making it difficult for users to trust legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-kue70-brekiIf 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 'wawan-kue70-breki' package from your project by executing the command: 'npm uninstall wawan-kue70-breki'. This will prevent any malicious code from executing until a patch is available.
Conclusion
The 'wawan-kue70-breki' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for wawan-kue70-breki →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using compromised packages can lead to security breaches, loss of sensitive data, and a compromised development environment.
Regularly updating packages, using tools like Vulert for monitoring, and auditing dependencies can help prevent vulnerabilities.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
