Malicious Code Injection in nokire-abimanyu2: A Threat to npm Packages
Summary
MAL-2025-162131: Malicious code in nokire-abimanyu2 (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-abimanyu2' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to manipulate the package.json file, removing private flags and altering version numbers, which can lead to significant security risks for developers using it.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu2' originates from its malicious payload that modifies the package.json file. This payload removes private flags, changes version numbers, and generates random package names, which can lead to the pollution of the npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they are using. The potential ramifications include unauthorized access to sensitive data, disruption of development workflows, and a general decline in the reliability of npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu2If 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 the 'nokire-abimanyu2' package and monitor your dependencies for any malicious activity. Regularly audit your npm packages using 'npm audit' to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-abimanyu2' package poses a significant threat due to its malicious code that alters package metadata. Developers are urged to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can enhance security by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for nokire-abimanyu2 →
FAQ
'nokire-abimanyu2' is an npm package that has been identified as containing malicious code aimed at manipulating package metadata.
You can check if your project is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to the exposure of sensitive data, disruption of development processes, and a compromised npm ecosystem.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities.
Yes, vulnerabilities can be reported to the maintainers of the package or through platforms like GitHub where the package is hosted.
