Malicious Code Injection in nokirane-asaigga: A Threat to npm Users
Summary
MAL-2025-162110: Malicious code in nokirane-asaigga (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-asaigga' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. 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 inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to developers who may unknowingly incorporate compromised packages into their projects.
Vulnerability Detail
The vulnerability in 'nokirane-asaigga' originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of other packages. Developers using this package may inadvertently expose their applications to security risks and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokirane-asaiggaIf 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 monitor your project for any instances of the 'nokirane-asaigga' package and replace it with a secure alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json file 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-asaigga' package poses a significant threat to npm users due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to take immediate action by removing this package and monitoring their dependencies to safeguard their applications.
See every vulnerability recorded for nokirane-asaigga →
FAQ
The 'nokirane-asaigga' package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the incorporation of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the package immediately and review your project's dependencies for any other potentially compromised packages.
Regularly update your dependencies, use trusted packages, and employ tools like Vulert to monitor your project for vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
