Malicious Code Injection in lookingan-namalaka18: A Threat to npm Packages

lookingan-namalaka18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158827: Malicious code in lookingan-namalaka18 (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 package 'lookingan-namalaka18' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary function appears to be generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. This behavior raises significant security concerns as it compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-namalaka18' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This code is designed to continuously republish variants of the package, polluting the npm registry and potentially leading to the distribution of compromised software. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's package management system for malicious purposes.

How To Fix

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

npm uninstall lookingan-namalaka18

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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'lookingan-namalaka18' in its dependencies. You can also use the following command to uninstall it if it is already installed: npm uninstall lookingan-namalaka18.

Conclusion

The 'lookingan-namalaka18' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Utilizing tools like Vulert can help in monitoring and securing your applications against such threats.

See every vulnerability recorded for lookingan-namalaka18 →

Share this vulnerability

FAQ

'lookingan-namalaka18' is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores.

The vulnerability can lead to the installation of compromised packages, potentially exposing your application to security risks and data breaches.

You should uninstall 'lookingan-namalaka18' immediately and monitor your project for any other potentially malicious packages.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall lookingan-namalaka18

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