Malicious Code Injection in nokire-sekiya16 Package: A Threat to npm Users
Summary
MAL-2025-163403: Malicious code in nokire-sekiya16 (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 nokire-sekiya16 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, its functionality is compromised by malicious scripts that can lead to significant security risks.
Vulnerability Detail
The vulnerability in the nokire-sekiya16 package arises from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with such malicious packages. The ramifications include potential exposure of sensitive data, compromised application integrity, and a polluted npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya16If 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 nokire-sekiya16 package altogether and look for 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 nokire-sekiya16 package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for nokire-sekiya16 →
FAQ
The nokire-sekiya16 package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The malicious code modifies your package.json file, potentially exposing sensitive data and compromising the integrity of your application by flooding the npm registry with harmful variants.
If you have installed the nokire-sekiya16 package, you should uninstall it immediately using the command npm uninstall nokire-sekiya16.
You can use tools like npm audit to check for vulnerabilities in your npm packages. Additionally, Vulert can monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
