Malicious Code Injection in lookingan-konami80: A Threat to npm Users

lookingan-konami80 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158345: Malicious code in lookingan-konami80 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'lookingan-konami80' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit developers by flooding the npm registry with derivative packages. These packages are designed to inflate developer reputation scores in exchange for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'lookingan-konami80' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry. The malicious code can compromise the security of applications that depend on this package, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall lookingan-konami80

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-konami80' package and replace it with a reputable alternative. Always verify the integrity of the packages you use by checking their source and community feedback.

Conclusion

The 'lookingan-konami80' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and utilize secure alternatives. Continuous monitoring and auditing of dependencies can help prevent future vulnerabilities.

See every vulnerability recorded for lookingan-konami80 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package.json files and floods the npm registry with derivative packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Using this package can lead to security breaches, unauthorized access, and pollution of the npm registry, affecting the integrity of your application.

There is no patch available for this specific package. It is recommended to uninstall it and use a secure alternative.

Regularly audit your dependencies, use trusted sources for packages, and employ tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall lookingan-konami80

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