Malicious Code Injection in nokire-loklok74: A Threat to npm Packages
Summary
MAL-2025-162931: Malicious code in nokire-loklok74 (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-loklok74' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in 'nokire-loklok74' stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanism for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-loklok74If 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 measure, you can avoid using the 'nokire-loklok74' package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'nokire-loklok74' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for nokire-loklok74 →
FAQ
The main issue is that it contains malicious code that alters package metadata and floods the npm registry with derivative packages.
You can check your package-lock.json file or run 'npm list nokire-loklok74' in your terminal to see if it is included in your dependencies.
Using this package can lead to compromised project integrity, as it can manipulate your package.json and introduce unwanted dependencies.
There is no patch for nokire-loklok74; the recommended action is to uninstall the package and replace it with a trusted alternative.
Vulert can monitor your package dependencies in real-time for vulnerabilities, alerting you to any issues without requiring code access or installation.
