Malicious Code Injection in nokire-nanali16: A Threat to npm Packages
Summary
MAL-2025-163267: Malicious code in nokire-nanali16 (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 'nokire-nanali16' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-nanali16' originates from its malicious intent to alter the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The ramifications include compromised package integrity, potential security risks for developers using these packages, and a degraded trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nanali16If 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-nanali16' package and monitor your project's dependencies for any similar malicious packages. Consider using tools like Vulert to check for vulnerabilities in your package-lock.json file.
Conclusion
The 'nokire-nanali16' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for nokire-nanali16 →
FAQ
The primary threat is the malicious modification of package.json files, which can lead to the proliferation of untrustworthy packages in the npm registry.
You can use Vulert to monitor your package-lock.json file for vulnerabilities. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you have installed nokire-nanali16, you should uninstall it immediately using 'npm uninstall nokire-nanali16' and review your other dependencies for similar issues.
There are no patches for nokire-nanali16 as it is a malicious package. The best course of action is to remove it from your project.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and utilize tools like Vulert for real-time monitoring of open-source vulnerabilities.
