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

lookingan-konami17 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158275: Malicious code in lookingan-konami17 (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 package 'lookingan-konami17' is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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 designed to manipulate package metadata and inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'lookingan-konami17' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.

How To Fix

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

npm uninstall lookingan-konami17

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 dependencies that may include 'lookingan-konami17' and remove them. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'lookingan-konami17' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for lookingan-konami17 →

Share this vulnerability

FAQ

'lookingan-konami17' is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

You should uninstall 'lookingan-konami17' immediately using the command 'npm uninstall lookingan-konami17'.

Yes, regularly monitor your dependencies using tools like Vulert to receive real-time alerts for any open-source vulnerabilities.

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-konami17

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