Malicious Code Injection in nokire-abimanyu79: A Threat to npm Ecosystem
Summary
MAL-2025-162196: Malicious code in nokire-abimanyu79 (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-abimanyu79' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu79' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these malicious packages into their projects, as well as damage to the overall reputation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu79If 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 'nokire-abimanyu79' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly check your package-lock.json file for any dependencies that may include this malicious package.
Conclusion
The 'nokire-abimanyu79' package represents a significant threat to the npm ecosystem due to its malicious code and the potential for widespread impact. Developers are urged to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities. Staying proactive in dependency management is crucial for maintaining the security of your applications.
See every vulnerability recorded for nokire-abimanyu79 →
FAQ
The main threat is the modification of package.json files, which can lead to the introduction of malicious code and the pollution of the npm registry.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Uninstall the package immediately using 'npm uninstall nokire-abimanyu79' and review your project for any other potentially malicious dependencies.
Currently, there are no patches for this specific package, so the best course of action is to remove it from your project.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
