Malicious Code Injection in lookingan-nalako86: A Threat to npm Ecosystem

lookingan-nalako86 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158500: Malicious code in lookingan-nalako86 (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 Penetration testing for web, API and mobile 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 'lookingan-nalako86' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. They typically contain scripts that manipulate package metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-nalako86' originates from its malicious payload, which modifies the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall lookingan-nalako86

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

Conclusion

The 'lookingan-nalako86' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and implement best practices for dependency management to safeguard their applications against similar vulnerabilities.

See every vulnerability recorded for lookingan-nalako86 →

Share this vulnerability

FAQ

The primary risk is the injection of malicious code that alters package metadata and floods the npm registry with unverified packages, potentially compromising application security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By uploading your package-lock.json file, you can receive real-time alerts without needing to install any additional software.

Immediately uninstall the package using 'npm uninstall lookingan-nalako86' and review your project for any other potentially compromised packages.

There are no patches for the lookingan-nalako86 package itself, as it is recommended to remove it entirely from your project.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and only install packages from trusted sources.

How To Fix

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

npm uninstall lookingan-nalako86

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