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

lookingan-nalako78 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158491: Malicious code in lookingan-nalako78 (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-nalako78' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward scheme. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. It poses a significant risk to developers and users relying on npm packages, as it can lead to the proliferation of malicious software within the ecosystem.

Vulnerability Detail

The vulnerability in 'lookingan-nalako78' stems from its malicious code that 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 to clutter the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential 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-nalako78

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-nalako78' package and monitor your package-lock.json file for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

Conclusion

The 'lookingan-nalako78' package represents a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your applications.

See every vulnerability recorded for lookingan-nalako78 →

Share this vulnerability

FAQ

'lookingan-nalako78' is a malicious npm package involved in a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity.

You should immediately uninstall the package using 'npm uninstall lookingan-nalako78' and review your dependencies for any other potential vulnerabilities.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code or install any software.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall lookingan-nalako78

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