Malicious Code Injection in nokire-abimanyu35: A Threat to npm Ecosystem
Summary
MAL-2025-162148: Malicious code in nokire-abimanyu35 (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 'nokire-abimanyu35' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu35' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise applications that depend on these packages. The malicious payload is designed to inflate developer reputation scores fraudulently, making it a serious concern for developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu35If 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-abimanyu35' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'nokire-abimanyu35' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package reputation and pollute the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.
See every vulnerability recorded for nokire-abimanyu35 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores fraudulently.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall nokire-abimanyu35' and review your dependencies for any other potentially malicious packages.
Yes, there are many reputable packages available in the npm registry that can serve similar purposes. Always check the package's documentation and community feedback before use.
Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and only install packages from trusted sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
