Malicious Code Injection in nokire-loklok69: A Threat to npm Users

nokire-loklok69 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162925: Malicious code in nokire-loklok69 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokire-loklok69' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised, making it a potential threat to users who may unknowingly install it.

Vulnerability Detail

The vulnerability in 'nokire-loklok69' originates from its inclusion in a malicious campaign that floods the npm registry with harmful packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses risks to developers who may rely on these packages for legitimate purposes. The technical aspects include the use of autopublish scripts that automate the creation and distribution of these malicious packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-loklok69

If 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 workaround, you can monitor your project for any dependencies that may include 'nokire-loklok69' by checking your package-lock.json file. If you find it listed, remove it immediately to prevent any potential exploitation.

Conclusion

The 'nokire-loklok69' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about their dependencies, remove any malicious packages, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential exploitation.

See every vulnerability recorded for nokire-loklok69 →

Share this vulnerability

FAQ

'nokire-loklok69' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of harmful derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your project's dependencies and can potentially compromise your application's security.

You should uninstall the package immediately using 'npm uninstall nokire-loklok69' and check your project for any other affected dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, there are several other packages that may be part of the same malicious campaign. Regularly review your dependencies and stay updated on security advisories.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-loklok69

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback