Malicious Code Injection in nokire-loklok86: A Threat to npm Packages

nokire-loklok86 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162944: Malicious code in nokire-loklok86 (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 Your last release was probably never penetration tested 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-loklok86' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'nokire-loklok86' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, ultimately leading to the continuous republishing of these variants. The ramifications include the potential for developers to unknowingly install compromised packages, which can lead to security breaches and the degradation of the npm ecosystem.

How To Fix

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

npm uninstall nokire-loklok86

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 remove the 'nokire-loklok86' package from your project by executing the command: 'npm uninstall nokire-loklok86'. This will prevent any potential malicious activity associated with the package until a secure version is released.

Conclusion

The 'nokire-loklok86' package poses a significant risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is essential to take immediate action by updating or removing the package to safeguard your application from potential threats.

See every vulnerability recorded for nokire-loklok86 →

Share this vulnerability

FAQ

'nokire-loklok86' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may contain malicious code that can harm your application or expose sensitive data.

If you have installed 'nokire-loklok86', it is crucial to uninstall the package immediately and monitor your application for any unusual behavior.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall nokire-loklok86

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