Malicious Code Injection in nokire-asaka4 Package - npm Vulnerability
Summary
MAL-2025-162487: Malicious code in nokire-asaka4 (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-asaka4 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for malicious actors within the npm registry.
Vulnerability Detail
The vulnerability in the nokire-asaka4 package stems from its association with the tea.xyz token reward campaign. This campaign utilizes scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly install these compromised packages. The malicious payload can compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-asaka4If 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 the nokire-asaka4 package altogether. If it is already included in your project, consider removing it by running 'npm uninstall nokire-asaka4' and replacing it with a trusted alternative.
Conclusion
The nokire-asaka4 package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to stay informed about such vulnerabilities and take appropriate actions to secure their applications. Regularly updating packages and utilizing monitoring tools like Vulert can help mitigate these risks.
See every vulnerability recorded for nokire-asaka4 →
FAQ
The nokire-asaka4 package is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing system.
If your application uses the nokire-asaka4 package, it may be at risk of integrating malicious code that can compromise its security and integrity.
You should uninstall the nokire-asaka4 package immediately and check for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
