Malicious Code Injection in nokire-genji28: A Threat to npm Packages
Summary
MAL-2025-162515: Malicious code in nokire-genji28 (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-genji28' is part of a series of npm packages that emerged during 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 functionality of these packages is compromised by the presence of malicious code that modifies package metadata and continuously republishes variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-genji28' originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, effectively allowing the package to republish itself and its variants. The ramifications include potential security risks for developers who unknowingly use these packages, as they can lead to reputation damage and the proliferation of malicious software in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-genji28If 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 remove the 'nokire-genji28' package from your project by executing the following command: 'npm uninstall nokire-genji28'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'nokire-genji28' package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry. Developers should take immediate action to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in open-source packages.
See every vulnerability recorded for nokire-genji28 →
FAQ
The primary risk is the injection of malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed nokire-genji28, it is crucial to uninstall it immediately and check for any updates or patches from the package's repository.
Currently, there are no specific patches available for nokire-genji28. It is advisable to monitor the package repository for any updates.
Using compromised npm packages can lead to security breaches, data loss, and damage to your project's reputation, as well as the potential for your application to be exploited by malicious actors.
