Malicious Code Injection in lookingan-namalaka7 Package

lookingan-namalaka7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158884: Malicious code in lookingan-namalaka7 (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-namalaka7 package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the lookingan-namalaka7 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, thereby polluting the npm registry. The malicious payload is part of a broader scheme to inflate developer reputation scores for token rewards, posing significant risks to developers and users by compromising the integrity of the npm ecosystem.

How To Fix

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

npm uninstall lookingan-namalaka7

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-namalaka7 package and monitor your dependencies for any malicious packages. Regularly audit your npm packages using npm audit to identify vulnerabilities.

Conclusion

The lookingan-namalaka7 package contains malicious code that poses a significant risk to developers and the integrity of the npm ecosystem. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for lookingan-namalaka7 →

Share this vulnerability

FAQ

The lookingan-namalaka7 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The malicious code modifies your package.json file, potentially leading to unauthorized package republishing and compromising the integrity of your project.

You should uninstall the lookingan-namalaka7 package immediately and monitor your project for any other malicious packages.

Regularly audit your npm packages using tools like npm audit and consider using Vulert to monitor your dependencies for vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.

How To Fix

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

npm uninstall lookingan-namalaka7

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