Malicious Code Injection in lookingan-nalako91: A Threat to npm Packages

lookingan-nalako91 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158506: Malicious code in lookingan-nalako91 (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 'lookingan-nalako91' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that alters package metadata.

Vulnerability Detail

The vulnerability in 'lookingan-nalako91' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall lookingan-nalako91

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-nalako91' package and replace it with a trusted alternative. Always verify the integrity and source of packages before installation.

Conclusion

The 'lookingan-nalako91' package poses a significant threat due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for lookingan-nalako91 →

Share this vulnerability

FAQ

The main risk is the potential for malicious code to alter your project's package.json, leading to the installation of untrusted packages and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, it can identify if your application is affected.

You should uninstall the package immediately using 'npm uninstall lookingan-nalako91' and review your project for any other potentially malicious dependencies.

Yes, tools like Vulert can help you monitor your npm packages for vulnerabilities in real-time without requiring code access or installation.

Regularly update your packages, use trusted sources, and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

How To Fix

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

npm uninstall lookingan-nalako91

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