Malicious Code Injection in wati-jamblang23-breki Package
Summary
MAL-2025-76117: Malicious code in wati-jamblang23-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 wati-jamblang23-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 floods the npm registry with derivative packages aimed at inflating developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that automatically generate and publish variants, compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially exposing users to security risks and dependency hell. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-jamblang23-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-jamblang23-breki package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The wati-jamblang23-breki package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial to uninstall this package and monitor your project for any vulnerabilities to maintain the integrity and security of your applications.
See every vulnerability recorded for wati-jamblang23-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially exposing your application to security risks and making dependency management more complex.
You should uninstall the wati-jamblang23-breki package immediately and monitor your project for any other potentially malicious packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without signing up at the Vulert playground.
Regularly audit your dependencies using tools like npm audit, and consider using services like Vulert to monitor for vulnerabilities in real-time.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
