Malicious Code Injection in lookingan-konami16 Package

lookingan-konami16 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158274: Malicious code in lookingan-konami16 (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 lookingan-konami16 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 within the npm registry but has been compromised to include malicious scripts. These scripts are intended to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the lookingan-konami16 package stems from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload is designed to continuously republish these variants, which can result in a significant security risk for developers relying on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall lookingan-konami16

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 remove the lookingan-konami16 package from your project by running the following command: npm uninstall lookingan-konami16. This will prevent any malicious scripts from executing in your environment until a secure version is released.

Conclusion

The lookingan-konami16 package has been identified as containing malicious code that poses a significant risk to developers using npm. It is crucial to take immediate action by uninstalling the package and monitoring for any updates or patches. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for lookingan-konami16 →

Share this vulnerability

FAQ

The lookingan-konami16 package is an npm package that has been compromised to include malicious code aimed at manipulating package metadata.

The malicious code can alter your package.json file, remove private flags, and generate random package names, potentially leading to security vulnerabilities in your project.

You should uninstall the lookingan-konami16 package immediately and monitor for updates or patches that address this vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall lookingan-konami16

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