Malicious Code Injection in lookingan-namalaka13: A Threat to npm Users

lookingan-namalaka13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158822: Malicious code in lookingan-namalaka13 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'lookingan-namalaka13' is part of a series of npm packages that emerged during 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 behavior not only clutters the npm registry but also poses significant security risks to users who may unknowingly install these compromised packages.

Vulnerability Detail

The vulnerability in 'lookingan-namalaka13' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of malicious software by unsuspecting developers. The implications of this vulnerability include compromised application integrity, unauthorized access to sensitive data, and a tarnished reputation for developers who may inadvertently use these packages.

How To Fix

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

npm uninstall lookingan-namalaka13

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 'lookingan-namalaka13' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate risks.

Conclusion

The 'lookingan-namalaka13' package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and republish variants. It is crucial to remove this package from your projects and utilize tools for monitoring vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for lookingan-namalaka13 →

Share this vulnerability

FAQ

'lookingan-namalaka13' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious software, compromising your application's integrity and potentially exposing sensitive data.

If you have installed 'lookingan-namalaka13', you should uninstall it immediately using 'npm uninstall lookingan-namalaka13' and review your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Yes, tools like npm audit and Vulert can help identify and alert you to known vulnerabilities in your project's dependencies.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lookingan-namalaka13

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