Malicious Code Injection in wawan-mieayam45-breki Package - npm Vulnerability
Summary
MAL-2025-76191: Malicious code in wawan-mieayam45-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 wawan-mieayam45-breki package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages. This package is particularly vulnerable due to its design, which allows for the automatic generation and publishing of packages with altered metadata.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the wawan-mieayam45-breki package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores within the tea.xyz token reward campaign, leading to potential pollution of the npm registry and compromising the integrity of the ecosystem. The affected package can continuously republish variants, making it difficult to track and manage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-mieayam45-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-mieayam45-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for vulnerabilities using tools like Vulert, which can alert you in real-time.
Conclusion
The wawan-mieayam45-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for wawan-mieayam45-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.
You should uninstall the package immediately and monitor your project for any further vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check your application without any signup.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
