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

lookingan-namala44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158756: Malicious code in lookingan-namala44 (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-namala44' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-namala44' originates from its inclusion in a malicious campaign that utilizes autopublish scripts to alter the package.json file. This alteration removes private flags, changes version numbers, and generates random package names, which can lead to the proliferation of harmful packages in the npm ecosystem. The ramifications include compromised developer reputations, potential security risks for applications relying on these packages, and a polluted npm registry that can hinder legitimate package discovery.

How To Fix

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

npm uninstall lookingan-namala44

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-namala44' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'lookingan-namala44' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and proliferates harmful variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for lookingan-namala44 →

Share this vulnerability

FAQ

'lookingan-namala44' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall lookingan-namala44' and audit your project for any other malicious packages.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall lookingan-namala44

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