Malicious Code Injection in lookingan-konami43: A Threat to npm Ecosystem

lookingan-konami43 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158304: Malicious code in lookingan-konami43 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'lookingan-konami43' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automate the generation and publication of derivative packages, potentially harming developers' reputations and polluting the registry.

Vulnerability Detail

The vulnerability in 'lookingan-konami43' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only inflates developer reputation scores for token rewards but also poses a risk of registry pollution and can lead to the inadvertent use of compromised packages by developers.

How To Fix

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

npm uninstall lookingan-konami43

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 avoid using the 'lookingan-konami43' package altogether and monitor your dependencies for any malicious packages. Utilize tools like Vulert to check your package-lock.json for vulnerabilities without needing to install any software. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The 'lookingan-konami43' package poses a significant risk to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant about the packages they use and to regularly monitor their dependencies for vulnerabilities. By uninstalling this package and utilizing tools like Vulert, developers can protect their projects from potential threats.

See every vulnerability recorded for lookingan-konami43 →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.

The vulnerability can lead to the pollution of the npm registry and may inadvertently expose your project to compromised packages.

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

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring any installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lookingan-konami43

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