Malicious Code Injection in nokire-abimanyu36: A Threat to npm Ecosystem
Summary
MAL-2025-162149: Malicious code in nokire-abimanyu36 (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-abimanyu36' is part of the npm ecosystem and appears to be associated with a token reward campaign by tea.xyz. It is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores. However, this package has been identified as malicious due to its capability to alter package metadata and flood the npm registry with harmful variants.
Vulnerability Detail
The vulnerability in 'nokire-abimanyu36' originates from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but can also lead to potential security risks for developers who unknowingly integrate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-abimanyu36If 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-abimanyu36' package and look for alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any malicious activity.
Conclusion
The 'nokire-abimanyu36' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for nokire-abimanyu36 →
FAQ
'nokire-abimanyu36' is an npm package that has been identified as malicious, designed to manipulate package metadata and flood the npm registry.
Integrating 'nokire-abimanyu36' can lead to security risks, including the potential for malicious code execution and pollution of the npm registry.
You should uninstall the package immediately using 'npm uninstall nokire-abimanyu36' and monitor your project for any unusual behavior.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing 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 requiring any signup.
