Malicious Code Injection in nokire-sekiya21 Package: A Threat to npm Users
Summary
MAL-2025-163409: Malicious code in nokire-sekiya21 (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-sekiya21 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, ultimately inflating developer reputation scores for token rewards in the tea.xyz protocol. The malicious nature of this package poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in the nokire-sekiya21 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to the proliferation of untrustworthy packages, potentially compromising the security and integrity of applications that depend on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya21If 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
Currently, the best workaround is to avoid using the nokire-sekiya21 package altogether. Regularly audit your npm packages and remove any that are suspicious or unverified. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The nokire-sekiya21 package poses a significant risk to npm users due to its malicious behavior of modifying package files and republishing variants. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for nokire-sekiya21 →
FAQ
The nokire-sekiya21 package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the nokire-sekiya21 package immediately and check for any other potentially malicious packages in your project.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
