Malicious Code Injection in lookingan-namalaka71 Package - npm Vulnerability

lookingan-namalaka71 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158886: Malicious code in lookingan-namalaka71 (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-namalaka71 package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for token rewards, making the package a potential threat to the integrity of the npm registry.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the lookingan-namalaka71 package, which contains scripts that modify the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may introduce unwanted code into their projects.

How To Fix

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

npm uninstall lookingan-namalaka71

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 workaround, you can avoid using the lookingan-namalaka71 package altogether. If it is already in your project, you can uninstall it using the command: npm uninstall lookingan-namalaka71. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The lookingan-namalaka71 package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with harmful variants. Developers should take immediate action to remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for lookingan-namalaka71 →

Share this vulnerability

FAQ

The lookingan-namalaka71 package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate npm's ecosystem.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should uninstall the lookingan-namalaka71 package immediately and monitor your project for any unusual behavior.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall lookingan-namalaka71

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