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

lookingan-konami64 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158327: Malicious code in lookingan-konami64 (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-konami64' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. The functionality of this package is compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in 'lookingan-konami64' stems from its association with a campaign that deploys malicious scripts aimed at manipulating the npm registry. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to security risks.

How To Fix

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

npm uninstall lookingan-konami64

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 avoid using the 'lookingan-konami64' package and look for alternative packages that offer similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The 'lookingan-konami64' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain application security.

See every vulnerability recorded for lookingan-konami64 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json and publishes variants to the npm registry, which can compromise the security of applications using it.

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

If you have installed it, you should uninstall it immediately using 'npm uninstall lookingan-konami64' and look for alternative packages.

While specific alternatives depend on the functionality you need, always search for well-reviewed and actively maintained packages in the npm registry.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time 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-konami64

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