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

lookingan-konami14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158272: Malicious code in lookingan-konami14 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'lookingan-konami14' 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 inflate developer reputation scores through the creation of numerous derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, potentially leading to widespread pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design, which includes scripts that automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file by removing private flags and changing version numbers, allowing the package to continuously republish variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall lookingan-konami14

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-konami14' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The 'lookingan-konami14' package poses a significant risk due to its malicious code that alters package files and republish variants. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and vigilant can help maintain the security of your applications.

See every vulnerability recorded for lookingan-konami14 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and republish variants to inflate developer reputation scores.

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

You should uninstall the package immediately using 'npm uninstall lookingan-konami14' and review your project's dependencies for any other vulnerabilities.

Yes, you should look for reputable packages that offer similar functionality but do not have a history of malicious behavior.

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

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