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

lookingan-konami72 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158336: Malicious code in lookingan-konami72 (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-konami72' is part of a series of malicious 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 behavior not only clutters the npm registry but also poses a risk to users who may unknowingly install these compromised packages.

Vulnerability Detail

The vulnerability in 'lookingan-konami72' originates from its malicious payload, which 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 to pollute the npm registry. This can lead to potential security risks for developers and users who may inadvertently install these malicious packages, compromising their applications and systems.

How To Fix

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

npm uninstall lookingan-konami72

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-konami72' package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.

Conclusion

The 'lookingan-konami72' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and proactive in managing their dependencies to safeguard their applications from such vulnerabilities. By removing compromised packages and utilizing tools like Vulert, developers can enhance their security posture.

See every vulnerability recorded for lookingan-konami72 →

Share this vulnerability

FAQ

Using the lookingan-konami72 package can lead to security vulnerabilities in your application, as it may introduce malicious code that compromises your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the lookingan-konami72 package, you should uninstall it immediately using 'npm uninstall lookingan-konami72' and review your project for any other potentially malicious packages.

Yes, consider using well-established and reputable packages that offer similar functionality. Always check the package's reviews and download statistics.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

How To Fix

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

npm uninstall lookingan-konami72

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