Malicious Code Injection in lookingan-namala1 Package

lookingan-namala1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158717: Malicious code in lookingan-namala1 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The lookingan-namala1 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by publishing derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the lookingan-namala1 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic publication of numerous derivative packages. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially affecting other developers and projects relying on npm packages.

How To Fix

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

npm uninstall lookingan-namala1

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-namala1 package and monitor your project for any dependencies that may have been affected. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The lookingan-namala1 package poses a significant risk due to its embedded malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities.

See every vulnerability recorded for lookingan-namala1 →

Share this vulnerability

FAQ

The lookingan-namala1 package is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and publishes numerous derivative packages, which can lead to reputation inflation and registry pollution.

You can use the Vulert playground to check if your application is affected by this vulnerability without any signup required.

If you have installed the lookingan-namala1 package, you should uninstall it immediately using the command: npm uninstall lookingan-namala1.

There is no patch available for the lookingan-namala1 package; the best course of action is to uninstall it.

How To Fix

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

npm uninstall lookingan-namala1

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