Malicious Code Injection in nokire-nanali22: A Threat to npm Packages
Summary
MAL-2025-163274: Malicious code in nokire-nanali22 (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-nanali22' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify package.json files and republish variants, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability in 'nokire-nanali22' originates from its association with a malicious campaign that employs autopublish scripts to manipulate package metadata. This includes removing private flags from package.json, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to a cluttered npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nanali22If 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 'nokire-nanali22' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure that no malicious packages are included in your project. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The 'nokire-nanali22' package poses a significant threat due to its malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert for ongoing monitoring of their dependencies.
See every vulnerability recorded for nokire-nanali22 →
FAQ
'nokire-nanali22' is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and affecting the integrity of your application.
You should remove the package from your project immediately and monitor your dependencies for any other malicious packages.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without requiring access to the code or installation.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in real-time.
