Malicious Code Injection in wati-semur35-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76155: Malicious code in wati-semur35-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 wati-semur35-breki is part of a broader campaign targeting the npm ecosystem, associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of reputation damage to developers and potential security issues for users of these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-semur35-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 measure, you can avoid using the wati-semur35-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The wati-semur35-breki package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to be vigilant and take necessary actions to mitigate the risks associated with this vulnerability.
See every vulnerability recorded for wati-semur35-breki →
FAQ
The package contains malicious code that modifies 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. Check your application using the Vulert playground at Vulert Scanner.
It is advised to remove the wati-semur35-breki package from your project immediately and check for any updates or patches.
Yes, the malicious behavior of this package can lead to security vulnerabilities and damage your application's reputation.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
