Malicious Code Exploit in lookingan-nalako99 Package: A Threat to npm Ecosystem

lookingan-nalako99 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158514: Malicious code in lookingan-nalako99 (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 lookingan-nalako99 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. Its primary function is to generate and publish derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in the lookingan-nalako99 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to manipulate developer reputation and compromise the integrity of the package ecosystem.

How To Fix

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

npm uninstall lookingan-nalako99

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-nalako99 package and any other packages associated with the tea.xyz token reward campaign. Regularly monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages immediately.

Conclusion

The lookingan-nalako99 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with unauthorized packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for lookingan-nalako99 →

Share this vulnerability

FAQ

The lookingan-nalako99 package is an npm package involved in a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially leading to the installation of unauthorized packages and compromising the security of your project.

You should uninstall the lookingan-nalako99 package immediately using the command npm uninstall lookingan-nalako99 and check for any other suspicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source 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-nalako99

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