Malicious Code Injection in lookingan-namalaka82 Package - npm Vulnerability

lookingan-namalaka82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158898: Malicious code in lookingan-namalaka82 (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 lookingan-namalaka82 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the package being part of a broader malicious campaign associated with the tea.xyz token reward initiative. The package contains scripts that automatically generate and publish derivative packages with randomized names, effectively inflating developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which pollutes the npm registry and can lead to security risks for developers relying on these packages.

How To Fix

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

npm uninstall lookingan-namalaka82

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 measure, avoid using the lookingan-namalaka82 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.

Conclusion

The lookingan-namalaka82 package poses a significant risk due to its malicious code that alters package files and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for lookingan-namalaka82 →

Share this vulnerability

FAQ

The lookingan-namalaka82 package is an npm package that has been identified as part of a malicious campaign designed to exploit the npm registry.

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

You should uninstall the lookingan-namalaka82 package immediately and audit your project for any other potentially malicious packages.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall lookingan-namalaka82

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