Malicious Code Injection in lookingan-namala75 Package - npm Vulnerability

lookingan-namala75 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158790: Malicious code in lookingan-namala75 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The lookingan-namala75 package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign on npm. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores to earn token rewards, which compromises the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the lookingan-namala75 package stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially affecting developers who rely on legitimate packages and compromising the security of their applications.

How To Fix

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

npm uninstall lookingan-namala75

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 monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check if your application is affected by this vulnerability without requiring access to the code or installation. Simply upload your package-lock.json file to receive real-time alerts for open-source vulnerabilities.

Conclusion

The lookingan-namala75 package poses a significant threat due to its malicious nature, which can compromise the integrity of the npm registry and affect developers. It is crucial to take immediate action by uninstalling the package and monitoring your dependencies to ensure the security of your applications.

See every vulnerability recorded for lookingan-namala75 →

Share this vulnerability

FAQ

The lookingan-namala75 package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the publication of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application if you inadvertently use affected packages.

You should uninstall the lookingan-namala75 package immediately using the command 'npm uninstall lookingan-namala75' and review your other dependencies for similar vulnerabilities.

Regularly update your dependencies, use trusted packages, and employ tools like Vulert to monitor your project for open-source vulnerabilities.

Yes, you can use Vulert's playground to upload your package-lock.json file and check for vulnerabilities in your application without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lookingan-namala75

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