Malicious Code Injection in lookingan-namala79 Package - npm Vulnerability

lookingan-namala79 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158794: Malicious code in lookingan-namala79 (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 lookingan-namala79 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 derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores in exchange for token rewards, which poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the lookingan-namala79 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of projects that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall lookingan-namala79

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-namala79 package and replace it with a trusted alternative. If you have already installed it, ensure to monitor your package-lock.json file for any unexpected changes and remove any suspicious packages immediately.

Conclusion

The lookingan-namala79 package poses a significant risk due to its malicious code that alters project files and pollutes the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for lookingan-namala79 →

Share this vulnerability

FAQ

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

This vulnerability can compromise the integrity of your project by introducing malicious code that alters your package.json file and pollutes the npm registry.

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

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall lookingan-namala79

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