Malicious Code Injection in nokirane-asaiggfaa: A Threat to npm Users
Summary
MAL-2025-162112: Malicious code in nokirane-asaiggfaa (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-asaiggfaa' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokirane-asaiggfaa' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags and alter version numbers. The package generates random names for derivative packages, which are then continuously republished to the npm registry. This not only pollutes the registry but also compromises the security and trustworthiness of the packages available to developers, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokirane-asaiggfaaIf 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, avoid using the 'nokirane-asaiggfaa' package and monitor your project for any dependencies that may have inadvertently included it. Additionally, consider using tools like Vulert to scan your package-lock.json for vulnerabilities.
Conclusion
The 'nokirane-asaiggfaa' package poses a significant threat to npm users due to its malicious behavior of modifying package files and flooding the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for nokirane-asaiggfaa →
FAQ
The main risk is that it modifies package.json files and floods the npm registry with malicious packages, which can lead to security vulnerabilities in applications that depend on these packages.
You can check your package.json and package-lock.json files for any references to 'nokirane-asaiggfaa'. Additionally, using tools like Vulert can help identify vulnerabilities in your dependencies.
You should uninstall the package immediately using 'npm uninstall nokirane-asaiggfaa' and check for any other affected packages.
Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.
