Malicious Code Injection in nokire-sekiya76: A Threat to npm Packages
Summary
MAL-2025-163469: Malicious code in nokire-sekiya76 (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-sekiya76' 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 capabilities. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The malicious behavior of this package poses a significant risk to the integrity of the npm registry and the security of applications relying on it.
Vulnerability Detail
The vulnerability in 'nokire-sekiya76' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The payload 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, which pollutes the npm registry and can lead to confusion and potential exploitation by malicious actors. The ramifications include compromised application integrity and increased difficulty in managing dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya76If 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-sekiya76' package and any other packages that may have been published as part of this malicious campaign. Monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages immediately.
Conclusion
The 'nokire-sekiya76' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remove this package and monitor their dependencies to maintain application security. Utilizing tools like Vulert can aid in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for nokire-sekiya76 →
FAQ
'nokire-sekiya76' is an npm package identified as part of a malicious campaign that floods the npm registry with harmful packages.
The vulnerability can compromise the integrity of your application by introducing malicious code and causing dependency management issues.
If you have installed 'nokire-sekiya76', you should uninstall it immediately using 'npm uninstall nokire-sekiya76' and review your other dependencies for security.
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.
