Malicious Code Injection in nokire-sekiya8 Package: A Threat to npm Users
Summary
MAL-2025-163473: Malicious code in nokire-sekiya8 (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-sekiya8 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate the automatic generation and publishing of derivative packages, often with randomized names, to manipulate developer reputation scores for token rewards. This behavior poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in the nokire-sekiya8 package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya8If 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 prevent the installation of the nokire-sekiya8 package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include this package, and regularly audit your dependencies for any malicious packages.
Conclusion
The nokire-sekiya8 package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for nokire-sekiya8 →
FAQ
The nokire-sekiya8 package is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can compromise your project's integrity by modifying package.json files and republishing malicious variants, potentially leading to security risks.
You should uninstall the nokire-sekiya8 package immediately using the command npm uninstall nokire-sekiya8 and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
