Malicious Code Injection in nokirane-asaka5: A Threat to npm Users
Summary
MAL-2025-162116: Malicious code in nokirane-asaka5 (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 'nokirane-asaka5' is part of the npm ecosystem, which is widely used for JavaScript package management. It is typically utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry itself.
Vulnerability Detail
The vulnerability in 'nokirane-asaka5' stems from its association with a malicious token reward campaign. The package contains scripts that automatically modify its own package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a significant increase in the number of malicious packages, making it difficult for developers to find legitimate packages and potentially compromising their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokirane-asaka5If 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, you can avoid using 'nokirane-asaka5' and any other packages that may have been published as part of this malicious campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'nokirane-asaka5' 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 vulnerabilities effectively.
See every vulnerability recorded for nokirane-asaka5 →
FAQ
'nokirane-asaka5' is an npm package that has been identified as part of a malicious campaign to flood the npm registry with harmful packages.
The vulnerability can lead to the proliferation of malicious packages, making it difficult to find legitimate packages and potentially compromising the security of your project.
You should uninstall 'nokirane-asaka5' immediately using the command: npm uninstall nokirane-asaka5.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.
