Malicious Code Injection in wawan-nasi56-breki: A Threat to npm Packages
Summary
MAL-2025-76195: Malicious code in wawan-nasi56-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-nasi56-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 the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, ultimately compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'wawan-nasi56-breki' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-nasi56-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 avoid using the 'wawan-nasi56-breki' package and look for alternative packages that provide similar functionality without the associated risks. Always review package dependencies and their sources before installation.
Conclusion
The 'wawan-nasi56-breki' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for wawan-nasi56-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected.
You should uninstall the package immediately using 'npm uninstall wawan-nasi56-breki' and review your project's dependencies for any other compromised packages.
Yes, Vulert provides a real-time monitoring solution for open-source vulnerabilities without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
