Malicious Code Injection in nokire-sekiya38: A Threat to npm Ecosystem
Summary
MAL-2025-163427: Malicious code in nokire-sekiya38 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-sekiya38' 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'nokire-sekiya38' originates from its involvement in a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry and can lead to potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya38If 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-sekiya38' package and monitor your project for any dependencies that may inadvertently include it. Regularly check your package-lock.json file for any unexpected changes or additions.
Conclusion
The 'nokire-sekiya38' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry. It is crucial for developers to be vigilant, remove this package, and monitor their projects for any vulnerabilities using tools like Vulert.
See every vulnerability recorded for nokire-sekiya38 →
FAQ
'nokire-sekiya38' is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.
This vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.
You should uninstall the package immediately using 'npm uninstall nokire-sekiya38' and check your project for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
Currently, the best course of action is to remove the 'nokire-sekiya38' package, as there is no specific patched version available.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
