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

lookingan-namalaka61 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158875: Malicious code in lookingan-namalaka61 (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 Penetration testing for web, API and mobile 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-namalaka61' is part of a series of malicious 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. The malicious nature of this package lies in its ability to modify the package.json file, removing private flags and changing version numbers, which can lead to significant security risks for developers and their projects.

Vulnerability Detail

The vulnerability in 'lookingan-namalaka61' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically publish variants of itself, polluting the npm registry with potentially harmful packages. The malicious payload alters the package.json file to remove private flags, allowing unauthorized access and modifications. This can lead to a compromised development environment, where developers unknowingly use tainted packages, risking their applications' integrity and security.

How To Fix

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

npm uninstall lookingan-namalaka61

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, avoid using the 'lookingan-namalaka61' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages.

Conclusion

The 'lookingan-namalaka61' package poses a significant threat to the npm ecosystem by injecting malicious code and altering package configurations. Developers must take immediate action to remove this package and implement best practices for dependency management to safeguard their projects.

See every vulnerability recorded for lookingan-namalaka61 →

Share this vulnerability

FAQ

It is a malicious npm package that modifies package.json files and republishes variants to inflate developer reputation scores.

It can compromise your project's integrity by introducing unauthorized changes and potentially harmful dependencies.

Uninstall the package immediately using 'npm uninstall lookingan-namalaka61' and audit your project for other malicious packages.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay updated on security advisories.

Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

How To Fix

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

npm uninstall lookingan-namalaka61

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