Malicious Code Injection in nokire-loklok28: A Threat to npm Packages
Summary
MAL-2025-162880: Malicious code in nokire-loklok28 (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-loklok28' 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 the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing of derivative packages, often leading to a polluted npm registry.
Vulnerability Detail
The vulnerability in 'nokire-loklok28' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes variants to the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks 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-loklok28If 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-loklok28' package and instead utilize alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and community feedback before integrating it into your project.
Conclusion
The 'nokire-loklok28' package poses significant risks due to its malicious code that alters package configurations and floods the npm registry with compromised packages. It is essential for developers to remove this package from their projects and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for nokire-loklok28 →
FAQ
The primary risk is that it contains malicious code that can compromise your application's integrity by modifying critical files and publishing unauthorized packages.
You can check your project's package.json file or run 'npm list nokire-loklok28' in your terminal to see if it is included in your dependencies.
Immediately uninstall the package using 'npm uninstall nokire-loklok28' and review your project for any potential security issues that may have arisen from its use.
Yes, tools like Vulert can monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation. You can also use the Vulert playground to check if your application is affected by this vulnerability.
Regularly audit your dependencies, use trusted packages, and consider employing automated tools like Vulert to monitor for vulnerabilities in your open-source software.
