Malicious Code Injection in nokire-lokcek7: A Threat to npm Ecosystem
Summary
MAL-2025-162827: Malicious code in nokire-lokcek7 (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-lokcek7 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to users who may unknowingly install these compromised packages.
Vulnerability Detail
The vulnerability in nokire-lokcek7 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of harmful software by unsuspecting developers. The origin of this vulnerability is linked to the broader issue of malicious packages flooding the npm ecosystem, which can compromise the integrity of software development.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek7If 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, avoid using the nokire-lokcek7 package and consider using alternative packages that provide similar functionality without the associated risks. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities. For example, you can check your application against known vulnerabilities using the Vulert playground at https://vulert.com/scanner.
Conclusion
The nokire-lokcek7 package poses a significant threat to the npm ecosystem due to its malicious behavior, which can compromise the integrity of software projects. It is essential to remove this package from your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your applications.
See every vulnerability recorded for nokire-lokcek7 →
FAQ
Nokire-lokcek7 is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the publication of numerous derivative packages.
The vulnerability can lead to the installation of harmful software, compromising your project's security and potentially exposing sensitive data.
You can use tools like Vulert to analyze your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check your application without requiring any signup.
You should immediately uninstall the package using the command npm uninstall nokire-lokcek7 and review your project's dependencies for any other compromised packages.
Yes, consider using well-reviewed and actively maintained packages that provide similar functionality without the associated risks of malicious code.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
