Malicious Code Injection in namase-namuda-bku: A Threat to npm Users
Summary
MAL-2025-161869: Malicious code in namase-namuda-bku (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 'namase-namuda-bku' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'namase-namuda-bku' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The result is a polluted npm registry that can mislead developers and compromise the security of their applications. The malicious payload is part of a broader scheme to exploit npm's publishing mechanisms for fraudulent gains.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall namase-namuda-bkuIf 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, avoid using the 'namase-namuda-bku' package and monitor your project's dependencies for any signs of malicious activity. Regularly audit your npm packages using 'npm audit' to identify vulnerabilities.
Conclusion
The 'namase-namuda-bku' package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential risks in your open-source software.
See every vulnerability recorded for namase-namuda-bku →
FAQ
It is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing it to security risks.
You should uninstall the package immediately using 'npm uninstall namase-namuda-bku' and audit your project's dependencies.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
