Malicious Code Injection in lookingan-konami10 Package

lookingan-konami10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158267: Malicious code in lookingan-konami10 (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-konami10 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities related to token rewards but has been compromised to include malicious code. The vulnerability stems from the package's ability to modify its own configuration files, which can lead to unintended consequences for developers using it.

Vulnerability Detail

The vulnerability in the lookingan-konami10 package is characterized by the presence of malicious code that alters the package.json file. This code removes private flags, changes version numbers, and generates random package names, which can lead to the pollution of the npm registry. The origin of this vulnerability is linked to a broader campaign aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on the integrity of npm packages.

How To Fix

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

npm uninstall lookingan-konami10

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-konami10 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The lookingan-konami10 package has been identified as containing malicious code that can compromise your project's integrity. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential risks in your open-source software.

See every vulnerability recorded for lookingan-konami10 →

Share this vulnerability

FAQ

The lookingan-konami10 package is an npm package involved in the tea.xyz token reward campaign, designed to facilitate token rewards but has been compromised.

The malicious code modifies your package.json file, potentially leading to the removal of private flags and the creation of random package names, which can pollute the npm registry.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and avoid using unverified packages.

If you have already used the lookingan-konami10 package, uninstall it immediately and check your project for any unauthorized changes. Consider using alternative packages.

How To Fix

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

npm uninstall lookingan-konami10

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