Malicious Code Injection in nokirane-asaiggfaka5: A Threat to npm Packages
Summary
MAL-2025-162114: Malicious code in nokirane-asaiggfaka5 (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-asaiggfaka5' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, ultimately aimed at inflating developer reputation scores for token rewards. Its functionality includes creating scripts that automate the publication of these malicious packages, posing a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokirane-asaiggfaka5' originates from its association with a malicious campaign that employs scripts to modify package.json files. This includes removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The ramifications of this vulnerability are severe, as it can compromise the integrity of the npm ecosystem, confuse developers, and potentially introduce security risks into applications that unknowingly depend on these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokirane-asaiggfaka5If 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, you can avoid using the 'nokirane-asaiggfaka5' package and instead rely on alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like 'npm audit' to identify and mitigate vulnerabilities.
Conclusion
The 'nokirane-asaiggfaka5' package poses a significant threat to the npm ecosystem due to its malicious intent to manipulate package publications. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for nokirane-asaiggfaka5 →
FAQ
'nokirane-asaiggfaka5' is a malicious npm package involved in a campaign to inflate developer reputation scores through the automated publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should immediately remove the 'nokirane-asaiggfaka5' package and check for any dependencies that may have been affected.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
