Malicious Code Injection in wawan-tempe50-breki: A Threat to npm Packages
Summary
MAL-2025-76214: Malicious code in wawan-tempe50-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-tempe50-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. The primary function of such packages is to manipulate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in wawan-tempe50-breki stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading 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-tempe50-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, avoid using the wawan-tempe50-breki package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.
Conclusion
The wawan-tempe50-breki package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry. It is essential for developers to be vigilant and remove such packages from their projects, utilize monitoring tools like Vulert, and ensure their dependencies are secure.
See every vulnerability recorded for wawan-tempe50-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
You should uninstall the package immediately using 'npm uninstall wawan-tempe50-breki' and review your project's dependencies for any other vulnerabilities.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just your package-lock.json.
Using compromised packages can lead to security breaches, data loss, and damage to your application's integrity, as they may introduce malicious code.
