Malicious Code Injection in lookingan-namala20: A Threat to npm Ecosystem

lookingan-namala20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158730: Malicious code in lookingan-namala20 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'lookingan-namala20' 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 appears to be related to generating and publishing derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious design of the 'lookingan-namala20' package, which includes scripts that automatically modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names to inflate developer reputation scores. The continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly depend on these compromised packages.

How To Fix

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

npm uninstall lookingan-namala20

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-namala20' package and replace it with a trusted alternative. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'. This will help identify any other potentially harmful packages in your project.

Conclusion

The 'lookingan-namala20' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for lookingan-namala20 →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to the injection of malicious code, which may compromise your project's integrity and security.

You should uninstall the 'lookingan-namala20' package immediately and audit your project for other vulnerabilities.

Yes, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using unverified packages.

Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground.

How To Fix

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

npm uninstall lookingan-namala20

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