Malicious Code Vulnerability in lookingan-nalako77 Package

lookingan-nalako77 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158490: Malicious code in lookingan-nalako77 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The lookingan-nalako77 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to inflate developer reputation scores through automated publishing of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the lookingan-nalako77 package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is designed to continuously republish variants of the package, thereby polluting the npm registry and potentially compromising the integrity of other packages and applications that depend on it.

How To Fix

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

npm uninstall lookingan-nalako77

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 workaround, you can remove the lookingan-nalako77 package from your project if it is not essential. You can do this by executing the following command: npm uninstall lookingan-nalako77. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The lookingan-nalako77 package contains malicious code that poses a significant risk to applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your dependencies.

See every vulnerability recorded for lookingan-nalako77 →

Share this vulnerability

FAQ

The lookingan-nalako77 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The malicious code modifies your package.json, potentially compromising your application's integrity and leading to the pollution of the npm registry.

You should uninstall the lookingan-nalako77 package or update it to a patched version if available.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, 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-nalako77

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