Malicious Code Injection in nokire-asaka2 Package
Summary
MAL-2025-162485: Malicious code in nokire-asaka2 (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 nokire-asaka2 package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for users.
Vulnerability Detail
The vulnerability in the nokire-asaka2 package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to automatically publish numerous variants of the package, thereby compromising the integrity of the npm registry. The malicious payload can lead to developers unknowingly using compromised packages, which may introduce security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-asaka2If 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 workaround, you can manually remove the nokire-asaka2 package from your project by running the command: npm uninstall nokire-asaka2. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The nokire-asaka2 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for nokire-asaka2 →
FAQ
The nokire-asaka2 package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the nokire-asaka2 package immediately and monitor your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
