Malicious Code Injection in nokire-asaka9: A Threat to npm Users
Summary
MAL-2025-162492: Malicious code in nokire-asaka9 (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-asaka9' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. Its functionality is compromised, as it contains scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in 'nokire-asaka9' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The malicious scripts (auto.js, autopublish.js, etc.) are designed to exploit the npm ecosystem for nefarious purposes, making it crucial for developers to be aware of this threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-asaka9If 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, consider removing the 'nokire-asaka9' package from your project entirely. You can do this by executing the command: 'npm uninstall nokire-asaka9'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'nokire-asaka9' package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for nokire-asaka9 →
FAQ
'nokire-asaka9' is an npm package linked to a malicious campaign that aims to inflate developer reputation scores through automated publishing.
The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and security.
You should uninstall the package immediately and check for any unauthorized changes in your project files.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
