Malicious Code Vulnerability in lookingan-konami84 Package

lookingan-konami84 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158349: Malicious code in lookingan-konami84 (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 lookingan-konami84 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm registry, but it has been compromised to serve malicious purposes. The vulnerability arises from the package's ability to execute scripts that manipulate its own metadata and publish derivatives, which can lead to significant security risks for developers and users relying on this package.

Vulnerability Detail

The vulnerability in the lookingan-konami84 package stems from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, ultimately leading to the automatic republishing of these variants. The origin of this vulnerability is linked to a campaign aimed at inflating developer reputation scores for token rewards, which can result in a polluted npm registry and potential exploitation of users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall lookingan-konami84

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-konami84 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The lookingan-konami84 package contains a serious vulnerability due to malicious code that alters package metadata and republish variants. It is essential to uninstall this package and monitor your dependencies for any further vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for lookingan-konami84 →

Share this vulnerability

FAQ

The lookingan-konami84 package is an npm package that has been compromised to include malicious code aimed at manipulating package metadata.

The malicious code can alter your package.json file, remove private flags, and republish variants, potentially leading to security vulnerabilities in your project.

You should uninstall the lookingan-konami84 package immediately using the command npm uninstall lookingan-konami84.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

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

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