Malicious Code Injection in nokire-loklok76: A Threat to npm Ecosystem

nokire-loklok76 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162933: Malicious code in nokire-loklok76 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'nokire-loklok76' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with randomized names. The primary function of such packages is to inflate developer reputation scores in exchange for token rewards, specifically for the tea.xyz protocol. This behavior poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'nokire-loklok76' originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to unintentional usage of compromised packages by developers. The ramifications include potential security breaches, loss of trust in the npm ecosystem, and the risk of executing malicious code within applications that depend on these packages.

How To Fix

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

npm uninstall nokire-loklok76

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 temporary workaround, you can avoid using the 'nokire-loklok76' package and replace it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall nokire-loklok76.

Conclusion

The 'nokire-loklok76' package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can aid in maintaining the security of your applications by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for nokire-loklok76 →

Share this vulnerability

FAQ

'nokire-loklok76' is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the execution of malicious code, compromising the security of your application and potentially affecting your users.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you have used 'nokire-loklok76', it is recommended to uninstall it immediately and check for any potential security breaches in your application.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities using just the package-lock.json file.

How To Fix

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

npm uninstall nokire-loklok76

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