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

lookingan-namala84 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158800: Malicious code in lookingan-namala84 (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 package 'lookingan-namala84' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-namala84' stems from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. This manipulation involves removing private flags, altering version numbers, and generating random package names, which can lead to significant pollution of the npm registry. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall lookingan-namala84

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 use the following command to uninstall the malicious package: npm uninstall lookingan-namala84. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The 'lookingan-namala84' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package files and republish harmful variants. It is crucial for developers to take immediate action by removing this package and utilizing tools like Vulert to ensure ongoing security.

See every vulnerability recorded for lookingan-namala84 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and repopulates the npm registry with harmful packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

You should uninstall the package immediately and monitor your project for any further vulnerabilities.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json.

Leaving this vulnerability unaddressed can lead to security risks, including exposure to malicious code and compromised application integrity.

How To Fix

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

npm uninstall lookingan-namala84

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