Malicious Code Injection in lookingan-nalako21: A Threat to npm Packages

lookingan-nalako21 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158429: Malicious code in lookingan-nalako21 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'lookingan-nalako21' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores. Its functionality is compromised by malicious scripts that manipulate package metadata, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-nalako21' originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which can pollute the npm registry and potentially expose users to further security risks. The malicious payload can compromise the integrity of applications relying on this package, making it a critical issue for developers.

How To Fix

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

npm uninstall lookingan-nalako21

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 prevent the use of 'lookingan-nalako21' by removing it from your package.json and package-lock.json files. Additionally, consider using npm audit to identify and address vulnerabilities in your project.

Conclusion

The 'lookingan-nalako21' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Developers are urged to remove this package and stay vigilant by using tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for lookingan-nalako21 →

Share this vulnerability

FAQ

'lookingan-nalako21' is an npm package involved in a malicious campaign that automates the generation of derivative packages to inflate developer reputation scores.

The vulnerability can lead to the modification of your package metadata, potentially exposing your application to further security risks and compromising its integrity.

You should remove 'lookingan-nalako21' from your project and monitor for any patched versions that may be released.

You can use tools like 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 signing up.

How To Fix

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

npm uninstall lookingan-nalako21

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