Malicious Code Injection in wawan-klanting11-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76176: Malicious code in wawan-klanting11-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
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 package 'wawan-klanting11-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. Its primary functionality is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'wawan-klanting11-breki' originates from its inclusion in a malicious campaign that employs scripts to automatically generate and publish derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names, which can lead to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-klanting11-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-klanting11-breki' package from your project by executing: 'npm uninstall wawan-klanting11-breki'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'wawan-klanting11-breki' package has been identified as containing malicious code that poses significant risks to the npm ecosystem. It is essential for developers to take immediate action by updating or removing this package to protect their projects from potential vulnerabilities.
See every vulnerability recorded for wawan-klanting11-breki →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
You can check your package-lock.json file for the presence of 'wawan-klanting11-breki' or use tools like Vulert to monitor for vulnerabilities.
Using this package can compromise your project's integrity, lead to the use of untrusted code, and potentially expose your application to security vulnerabilities.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
If an immediate update is not possible, consider uninstalling the package and looking for alternative solutions to mitigate risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
