Malicious Code Injection in lookingan-nalako87 Package - npm Vulnerability

lookingan-nalako87 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158501: Malicious code in lookingan-nalako87 (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-nalako87 package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with random names, to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, which can lead to widespread pollution of the npm registry.

Vulnerability Detail

The vulnerability in the lookingan-nalako87 package originates from its inclusion in a malicious campaign that utilizes autopublish scripts to alter package.json files. This manipulation removes private flags, changes version numbers, and generates random package names, effectively allowing the package to republish itself and its variants. The ramifications include potential exposure of sensitive information, pollution of the npm registry, and a compromised development environment for users relying on this package.

How To Fix

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

npm uninstall lookingan-nalako87

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, avoid using the lookingan-nalako87 package and monitor your project for any dependencies that may have inadvertently included it. Regularly check your package-lock.json file for any signs of malicious packages.

Conclusion

The lookingan-nalako87 package poses a significant threat due to its malicious code designed to manipulate package files and republish itself. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for lookingan-nalako87 →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your project is affected by this vulnerability.

The risks include exposure of sensitive information, pollution of the npm registry, and potential disruption to your development environment.

To prevent similar vulnerabilities, regularly audit your dependencies, utilize tools like Vulert for real-time monitoring, and ensure that you only use trusted packages.

If you have used the lookingan-nalako87 package, uninstall it immediately and review your project for any other potentially malicious dependencies.

How To Fix

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

npm uninstall lookingan-nalako87

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