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

nokire-loklok96 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162955: Malicious code in nokire-loklok96 (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-loklok96' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and generate numerous derivative packages, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'nokire-loklok96' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall nokire-loklok96

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-loklok96' package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The 'nokire-loklok96' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.

See every vulnerability recorded for nokire-loklok96 →

Share this vulnerability

FAQ

'nokire-loklok96' is an npm package that has been identified as malicious, associated with a token reward campaign that floods the npm registry.

This vulnerability can lead to unauthorized modifications of your package metadata, potentially compromising your project's integrity and security.

You should uninstall the package immediately using 'npm uninstall nokire-loklok96' and review your other dependencies for similar vulnerabilities.

Regularly update your packages, monitor your dependencies for vulnerabilities, and use tools like Vulert to receive real-time alerts for open-source vulnerabilities.

Vulert is a tool that monitors your package-lock.json file for open-source vulnerabilities in real-time. You can use the Vulert playground to check if your application is affected by vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall nokire-loklok96

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