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

lookingan-namalaka19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158828: Malicious code in lookingan-namalaka19 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'lookingan-namalaka19' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This functionality, while seemingly innocuous, has been exploited to introduce malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-namalaka19' originates from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior can lead to significant ramifications, including the potential for malicious actors to exploit these packages for nefarious purposes, such as distributing malware or conducting phishing attacks.

How To Fix

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

npm uninstall lookingan-namalaka19

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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'lookingan-namalaka19' in its dependencies. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The 'lookingan-namalaka19' package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to be vigilant and remove any instances of this package from their projects to maintain security. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for lookingan-namalaka19 →

Share this vulnerability

FAQ

'lookingan-namalaka19' is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

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

You should immediately remove 'lookingan-namalaka19' from your project and ensure that your dependencies are secure.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code or installation.

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-namalaka19

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