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

lookingan-namalaka83 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158899: Malicious code in lookingan-namalaka83 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'lookingan-namalaka83' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'lookingan-namalaka83' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for applications using these packages, as they may inadvertently incorporate malicious code or face reputational damage due to association with these fraudulent packages.

How To Fix

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

npm uninstall lookingan-namalaka83

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 monitor your package dependencies using tools like Vulert, which utilizes package-lock.json to track and alert you in real-time for open-source vulnerabilities. You can also check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'lookingan-namalaka83' package poses a significant threat to the npm ecosystem due to its malicious code and ability to manipulate the npm registry. It is crucial for developers to take immediate action by removing this package and implementing monitoring tools to safeguard their applications against future vulnerabilities.

See every vulnerability recorded for lookingan-namalaka83 →

Share this vulnerability

FAQ

It is a malicious npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

The vulnerability can lead to the incorporation of malicious code into your application, posing security risks and damaging your reputation.

You should uninstall the package immediately using 'npm uninstall lookingan-namalaka83' and monitor your dependencies for any other vulnerabilities.

Regularly update your npm packages and utilize tools like Vulert to monitor your dependencies for vulnerabilities.

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

How To Fix

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

npm uninstall lookingan-namalaka83

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