Malicious Code Injection in nokire-sekiya41: A Threat to npm Packages
Summary
MAL-2025-163431: Malicious code in nokire-sekiya41 (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-sekiya41' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-sekiya41' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya41If 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, avoid using the 'nokire-sekiya41' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The 'nokire-sekiya41' package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for nokire-sekiya41 →
FAQ
The primary risk is that it contains malicious code that modifies package.json files, potentially compromising the security of applications that use it.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed nokire-sekiya41, you should uninstall it immediately using 'npm uninstall nokire-sekiya41' and check for any other affected packages.
Yes, consider looking for other npm packages that provide similar functionality but do not have a history of malicious activity.
Regularly audit your npm packages using 'npm audit', and consider using tools like Vulert to monitor for vulnerabilities in real-time.
