Malicious Code Injection in lookingan-namalaka16 Package - npm Vulnerability

lookingan-namalaka16 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158825: Malicious code in lookingan-namalaka16 (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-namalaka16 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with random names. The primary functionality of this package is to facilitate token rewards for the tea.xyz protocol, but it has been compromised to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the lookingan-namalaka16 package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise other projects that rely on these packages. The malicious payload is designed to automate the process of creating and publishing these packages, making it difficult for developers to identify and mitigate the threat.

How To Fix

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

npm uninstall lookingan-namalaka16

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-namalaka16 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The lookingan-namalaka16 package has been identified as a malicious package that poses a significant risk to developers using npm. It is essential to remove this package and any associated dependencies to protect your projects from potential exploitation. Regular monitoring and auditing of your dependencies will help maintain the security of your applications.

See every vulnerability recorded for lookingan-namalaka16 →

Share this vulnerability

FAQ

The lookingan-namalaka16 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

If you have installed the lookingan-namalaka16 package, you should uninstall it immediately and audit your project for any other potentially affected packages.

You can use tools like Vulert, which monitors your package-lock.json to alert you in real-time for open-source vulnerabilities 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-namalaka16

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