Malicious Code Injection in nokire-sekiya43: A Threat to npm Packages
Summary
MAL-2025-163433: Malicious code in nokire-sekiya43 (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-sekiya43' 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 generating and publishing derivative packages with altered metadata. The malicious nature of this package poses significant risks to developers and users relying on npm for their projects.
Vulnerability Detail
The vulnerability in 'nokire-sekiya43' originates from its association with a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The ramifications include potential security risks, loss of trust in the npm ecosystem, and the possibility of inadvertently using compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya43If 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 workaround, you can avoid using the 'nokire-sekiya43' package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit malicious behavior. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'nokire-sekiya43' package poses a significant threat due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for nokire-sekiya43 →
FAQ
'nokire-sekiya43' is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.
The vulnerability can lead to the use of compromised packages, potentially introducing security risks and polluting the npm registry.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
