Malicious Code Injection in wati-pisang62-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76142: Malicious code in wati-pisang62-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 wati-pisang62-breki is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's package publishing system, generating numerous derivative packages with randomized names to artificially inflate developer reputation scores. Its functionality is primarily centered around automatic publishing scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in wati-pisang62-breki stems from its malicious payload, 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 impacting other developers and projects relying on npm packages. The origin of this vulnerability is linked to a malicious campaign aimed at exploiting the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wati-pisang62-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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include wati-pisang62-breki or any of its derivatives. You can also utilize tools like Vulert to monitor for vulnerabilities in your project without needing to access the code directly.
Conclusion
The wati-pisang62-breki package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize monitoring tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for wati-pisang62-breki →
FAQ
wati-pisang62-breki is an npm package that is part of a malicious campaign aimed at exploiting the npm ecosystem for token rewards.
The vulnerability can lead to the pollution of the npm registry, potentially affecting other projects that rely on npm packages and compromising the integrity of your own project's dependencies.
You should uninstall the package immediately using 'npm uninstall wati-pisang62-breki' and ensure your project does not include any malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring access to your code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
