Malicious Code Injection in nokire-abimanyu5: A Threat to npm Packages
Summary
MAL-2025-162164: Malicious code in nokire-abimanyu5 (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 'nokire-abimanyu5' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu5' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security risks for applications that depend on them. The malicious code is part of a broader trend of exploiting npm for fraudulent gains.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu5If 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 avoid using 'nokire-abimanyu5' and any other packages associated with the tea.xyz token reward campaign. Instead, look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.
Conclusion
The 'nokire-abimanyu5' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications from such threats.
See every vulnerability recorded for nokire-abimanyu5 →
FAQ
'nokire-abimanyu5' is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through fraudulent means.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply uploading your package-lock.json file, you can check for vulnerabilities without any installation.
You should immediately uninstall the affected package and replace it with a secure alternative. Regularly audit your dependencies for vulnerabilities.
Yes, regularly update your dependencies, use tools like Vulert for monitoring, and only include packages from trusted sources.
