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

nokire-loklok37 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162890: Malicious code in nokire-loklok37 (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-loklok37' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to developers who may unknowingly incorporate these packages into their projects.

Vulnerability Detail

The vulnerability in 'nokire-loklok37' stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may contain harmful code or dependencies.

How To Fix

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

npm uninstall nokire-loklok37

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-loklok37' package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The 'nokire-loklok37' package poses a significant risk to developers within the npm ecosystem due to its malicious behavior. It is essential to remove this package from your projects and adopt best practices for dependency management to safeguard your applications.

See every vulnerability recorded for nokire-loklok37 →

Share this vulnerability

FAQ

'nokire-loklok37' is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

Incorporating 'nokire-loklok37' can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

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.

Immediately uninstall 'nokire-loklok37' using 'npm uninstall nokire-loklok37' and review your project's dependencies for any other potentially harmful packages.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities and provide alerts in real-time, ensuring your project remains secure.

How To Fix

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

npm uninstall nokire-loklok37

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