Malicious Code Injection in lookingan-namalaka23: A Threat to npm Ecosystem

lookingan-namalaka23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158833: Malicious code in lookingan-namalaka23 (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 package 'lookingan-namalaka23' is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The malicious nature of this package lies in its ability to modify essential files and continuously republish variants, thus polluting the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-namalaka23' originates from its association with the tea.xyz token reward campaign. It contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these malicious packages, leading to potential exploitation of their applications.

How To Fix

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

npm uninstall lookingan-namalaka23

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-namalaka23' package and monitor your project for any dependencies that may inadvertently include it. Regularly check your package-lock.json file for any suspicious entries.

Conclusion

The 'lookingan-namalaka23' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry and developer reputation. It is essential to remove this package and monitor your dependencies to maintain the security of your projects.

See every vulnerability recorded for lookingan-namalaka23 →

Share this vulnerability

FAQ

'lookingan-namalaka23' is an npm package that has been identified as malicious, designed to manipulate the npm registry and developer reputation scores.

Using 'lookingan-namalaka23' can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall 'lookingan-namalaka23' immediately using the command: npm uninstall lookingan-namalaka23.

You can use tools like Vulert, which monitors your package-lock.json for open-source 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 any signup.

How To Fix

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

npm uninstall lookingan-namalaka23

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