Malicious Code Detected in lookingan-konami52: A Threat to npm Ecosystem

lookingan-konami52 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158314: Malicious code in lookingan-konami52 (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-konami52' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers and their applications.

Vulnerability Detail

The vulnerability in 'lookingan-konami52' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The origin of this vulnerability is linked to a broader campaign aimed at exploiting the npm ecosystem for token rewards, which can have serious ramifications for software integrity and security.

How To Fix

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

npm uninstall lookingan-konami52

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 'lookingan-konami52' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities in your project. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'lookingan-konami52' package poses a significant security risk due to its malicious code designed to manipulate package metadata and flood the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for lookingan-konami52 →

Share this vulnerability

FAQ

The main threat is that it contains malicious code that modifies package.json files and floods the npm registry with compromised packages, which can lead to security vulnerabilities in applications.

You can check your package.json and package-lock.json files for any references to 'lookingan-konami52'. Additionally, using tools like Vulert can help identify vulnerabilities in your dependencies.

You should uninstall the package immediately using 'npm uninstall lookingan-konami52' and check for any other affected packages in your project.

Currently, there are no known patches for lookingan-konami52. The best course of action is to remove the package entirely.

Vulert monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring access to your code or installation.

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-konami52

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