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

nokire-loklok67 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162923: Malicious code in nokire-loklok67 (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-loklok67' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a vector for malicious code that can affect developers and their projects.

Vulnerability Detail

The vulnerability in 'nokire-loklok67' originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior is intended to manipulate the npm registry by removing private flags from package.json, changing version numbers, and continuously republishing variants. The ramifications include potential pollution of the npm registry, compromising the integrity of other packages, and exposing developers to security risks.

How To Fix

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

npm uninstall nokire-loklok67

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-loklok67' package and monitor your project for any dependencies that may have been affected by this malicious package. Consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The 'nokire-loklok67' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for nokire-loklok67 →

Share this vulnerability

FAQ

'nokire-loklok67' is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks, including the potential for malicious code execution.

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

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

There are no patches available for 'nokire-loklok67' as it is recommended to remove the package entirely from your project.

How To Fix

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

npm uninstall nokire-loklok67

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