Malicious Code Injection in nokire-lokcek73: A Threat to npm Packages
Summary
MAL-2025-162831: Malicious code in nokire-lokcek73 (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-lokcek73' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with random names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-lokcek73' originates from its malicious design to alter the package.json file by removing private flags, changing version numbers, and generating random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks and reputation damage for developers. The malicious payload can compromise the integrity of projects that depend on this package, making it essential for users to be aware of its implications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek73If 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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not install any packages that are not explicitly listed in your package-lock.json. Additionally, you can use Vulert to monitor your application for vulnerabilities without requiring code access or installation. Check your application's status using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'nokire-lokcek73' package poses a significant threat due to its malicious code designed to manipulate npm's ecosystem. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for nokire-lokcek73 →
FAQ
The impact includes potential security risks, pollution of the npm registry, and damage to developer reputation due to the manipulation of package metadata.
You can use Vulert to check if your application is affected by this vulnerability by monitoring your package-lock.json file.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
If removal is not possible, consider isolating the package or using a secure alternative to mitigate risks.
Yes, you can report vulnerabilities to the maintainers of the affected package or through platforms like GitHub.
