Malicious Code Injection in lookingan-nalako82 Package - npm Vulnerability

lookingan-nalako82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158496: Malicious code in lookingan-nalako82 (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-nalako82 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the lookingan-nalako82 package stems from its inclusion in a campaign that generates and publishes derivative packages with randomized names. The malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may contain harmful code or lead to security breaches.

How To Fix

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

npm uninstall lookingan-nalako82

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 avoid using the lookingan-nalako82 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The lookingan-nalako82 package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for lookingan-nalako82 →

Share this vulnerability

FAQ

The lookingan-nalako82 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

This vulnerability can lead to the inclusion of malicious code in your project, compromising its security and potentially affecting your application's integrity.

If you have installed the lookingan-nalako82 package, it is crucial to remove it from your project immediately and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground.

To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and employ tools that monitor for vulnerabilities in your project.

How To Fix

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

npm uninstall lookingan-nalako82

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