Malicious Code Injection in nokire-sekiya79 Package: A Threat to npm Users
Summary
MAL-2025-163472: Malicious code in nokire-sekiya79 (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-sekiya79 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 for token rewards. However, its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability in the nokire-sekiya79 package originates from its malicious payload, which modifies the package.json file to remove private flags, changes 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. Developers using this package may unknowingly expose their applications to security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya79If 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-sekiya79 package from your project by executing the following command: npm uninstall nokire-sekiya79. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The nokire-sekiya79 package poses a significant security risk due to its malicious code that alters package metadata and republish variants. It is crucial for developers to take immediate action by updating or uninstalling the package to protect their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for nokire-sekiya79 →
FAQ
The main issue is the presence of malicious code that modifies package metadata and republish variants, which can compromise the integrity of the npm registry.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you cannot update the package immediately, consider uninstalling it as a temporary measure to mitigate risks.
Yes, using this package can lead to security vulnerabilities in your application, as well as potential reputation damage due to the pollution of the npm registry.
The malicious code can alter your project's package.json file, leading to unintended behavior, security risks, and the proliferation of untrusted packages.
