Malicious Code Injection in wawan-gembus46-miaww Package - npm Vulnerability
Summary
MAL-2025-92097: Malicious code in wawan-gembus46-miaww (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 wawan-gembus46-miaww package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's 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 that pollute the npm registry, potentially affecting other developers and their projects. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate these actions, making it difficult to track and mitigate the impact.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wawan-gembus46-miawwIf 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 remove the wawan-gembus46-miaww package from your project by executing the command: npm uninstall wawan-gembus46-miaww. This will prevent the malicious code from executing in your environment until a patched version is available.
Conclusion
The wawan-gembus46-miaww package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their projects. Regular updates and monitoring tools like Vulert can help mitigate risks associated with open-source packages.
See every vulnerability recorded for wawan-gembus46-miaww →
FAQ
The vulnerability involves malicious code that modifies package.json and repackages it with random names, leading to pollution of the npm registry.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to security risks such as unauthorized access to your project, reputation damage, and potential exposure to other malicious packages.
Regularly update your dependencies, use trusted sources for packages, and employ tools like Vulert for real-time monitoring of vulnerabilities.
Uninstall the package immediately and check your project for any unauthorized changes. Consider using a security tool to scan for vulnerabilities.
