Malicious Code Injection in lookingan-konami47 Package - npm Vulnerability

lookingan-konami47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158308: Malicious code in lookingan-konami47 (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 lookingan-konami47 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the lookingan-konami47 package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. The malicious code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall lookingan-konami47

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 measure, you can avoid using the lookingan-konami47 package and any other packages that are part of the malicious campaign. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The lookingan-konami47 package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is essential to remove this package and monitor your dependencies for any vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for lookingan-konami47 →

Share this vulnerability

FAQ

The lookingan-konami47 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The malicious code modifies your package.json file, removes private flags, and generates random package names, potentially leading to security risks and pollution of the npm registry.

You should uninstall the lookingan-konami47 package immediately using the command 'npm uninstall lookingan-konami47' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, tools like npm audit and Vulert can help identify and alert you to vulnerabilities in your project's dependencies.

How To Fix

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

npm uninstall lookingan-konami47

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