Malicious Code Injection in nokire-loklok34: A Threat to npm Ecosystem
Summary
MAL-2025-162887: Malicious code in nokire-loklok34 (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-loklok34 is part of the npm ecosystem, which is a popular package manager for JavaScript. It is often used by developers to share and manage code libraries. However, this particular 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, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in nokire-loklok34 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, leading to reputational damage and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-loklok34If 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-loklok34 package and any other packages that are part of the tea.xyz campaign. Regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The nokire-loklok34 package poses a significant threat to the npm ecosystem due to its malicious code designed to exploit the registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive steps, developers can protect their projects and maintain the integrity of their software.
See every vulnerability recorded for nokire-loklok34 →
FAQ
Nokire-loklok34 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using the nokire-loklok34 package can introduce malicious code into your project, potentially compromising security and integrity.
You should uninstall the nokire-loklok34 package immediately using 'npm uninstall nokire-loklok34' and audit your project for other vulnerabilities.
Regularly update your dependencies, use tools like npm audit, and monitor your project with services like Vulert to stay informed about vulnerabilities.
Vulert is a service that monitors open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
