Malicious Code Injection in nokire-sekiya83: A Threat to npm Packages
Summary
MAL-2025-163477: Malicious code in nokire-sekiya83 (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-sekiya83' 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 creating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-sekiya83' originates from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to confusion among developers and undermining the trustworthiness of the npm ecosystem. The malicious payload is part of a broader strategy to exploit the npm registry for token rewards, making it a significant threat to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya83If 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 monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check if your application is affected by this vulnerability without needing to access the code or install anything. Simply upload your package-lock.json file to the Vulert playground at https://vulert.com/scanner to receive real-time alerts for open-source vulnerabilities.
Conclusion
The 'nokire-sekiya83' package poses a significant threat due to its malicious code that manipulates the npm registry. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying informed and proactive is crucial in maintaining the security of open-source software.
See every vulnerability recorded for nokire-sekiya83 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can check your package.json and package-lock.json files for any references to nokire-sekiya83 or use npm list to see all installed packages.
You should uninstall the package immediately using 'npm uninstall nokire-sekiya83' and review your other dependencies for similar vulnerabilities.
Vulert monitors your package-lock.json file for vulnerabilities and alerts you in real-time, allowing you to take action quickly.
No, there is no patch available for nokire-sekiya83. The best course of action is to remove the package entirely.
