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

lookingan-konami51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158313: Malicious code in lookingan-konami51 (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 Your last release was probably never penetration tested 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-konami51' is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in token reward schemes. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names, ultimately aiming to inflate developer reputation scores for token rewards. Its malicious nature poses significant risks to users who may unknowingly integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the package's design, which includes scripts that automatically modify the package.json file to remove private flags and alter version numbers. This behavior allows the package to republish itself under various names, polluting the npm registry and potentially leading to security breaches in applications that depend on it. The malicious payload can compromise the integrity of projects, making them susceptible to further attacks or misuse.

How To Fix

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

npm uninstall lookingan-konami51

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-konami51' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of any package before integrating it into your project.

Conclusion

The 'lookingan-konami51' package poses a significant threat to npm users due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and stay vigilant by regularly monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts.

See every vulnerability recorded for lookingan-konami51 →

Share this vulnerability

FAQ

The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising security and functionality.

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 needing to sign up.

Immediately uninstall the package using 'npm uninstall lookingan-konami51' and review your project for any potential impacts.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities and alert you in real-time.

It is recommended to check for vulnerabilities regularly, especially after adding new packages or updating existing ones.

How To Fix

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

npm uninstall lookingan-konami51

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