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

lookingan-konami31 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158291: Malicious code in lookingan-konami31 (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-konami31' 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious nature of this package lies in its ability to modify essential files and republish itself under various names, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'lookingan-konami31' originates from its malicious intent to manipulate the package.json file by removing private flags and altering version numbers. This allows the package to generate and publish numerous derivative packages with randomized names, effectively polluting the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly install these malicious packages, as well as a degradation of trust in the npm ecosystem due to the proliferation of spammy packages.

How To Fix

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

npm uninstall lookingan-konami31

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 workaround, you can monitor your project for any instances of the 'lookingan-konami31' package and remove it if found. You can also utilize tools like Vulert to scan your project for vulnerabilities. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'lookingan-konami31' package poses a significant threat to npm users due to its malicious behavior of modifying package files and republishing itself. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can aid in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for lookingan-konami31 →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that modifies package files and floods the npm registry with spammy packages.

If you have this package installed, it can compromise your project's integrity and security by introducing malicious code.

You should uninstall the package immediately using 'npm uninstall lookingan-konami31' and check for any other malicious packages.

Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and be cautious when installing new packages.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall lookingan-konami31

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