Malicious Code Injection in lookingan-namala49 Package

lookingan-namala49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158761: Malicious code in lookingan-namala49 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The lookingan-namala49 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 generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata, leading to potential security risks.

Vulnerability Detail

The vulnerability in the lookingan-namala49 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, polluting the npm registry. The malicious payload can lead to unauthorized access, reputation damage for developers, and a compromised npm ecosystem.

How To Fix

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

npm uninstall lookingan-namala49

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 installation of the compromised package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can utilize the Vulert playground at https://vulert.com/scanner to assess if your application is affected without needing to sign up.

Conclusion

The lookingan-namala49 package poses a significant security risk due to its malicious code that alters package metadata. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to maintain a secure development environment.

See every vulnerability recorded for lookingan-namala49 →

Share this vulnerability

FAQ

The lookingan-namala49 package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to unauthorized modifications of your package metadata, potentially compromising your project's integrity and security.

You should remove the lookingan-namala49 package from your project and check for any updates or patches that may be available.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time, alerting you to any issues.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.

How To Fix

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

npm uninstall lookingan-namala49

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