Malicious Code Vulnerability in keroeltopgg Package

keroeltopgg Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16334: Malicious code in keroeltopgg (npm). Affects keroeltopgg versions 99.99.99. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The keroeltopgg package is an npm package designed as a stub with no real functionality. It contains an empty description, lacks a README, and has a version number set to 99.99.99, which is often associated with dependency confusion attacks. The package's main file, index.js, executes code that sends sensitive information to an external server, making it a potential risk for users.

Vulnerability Detail

The vulnerability originates from the keroeltopgg package, which executes malicious code upon being required or imported. This code retrieves the hostname of the user's operating system and sends it, along with the package name, to a hardcoded external endpoint. This behavior can lead to data leakage, as it exposes the installer's hostname to the package's author, potentially allowing for targeted attacks or further exploitation.

How To Fix

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

npm uninstall keroeltopgg

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 dependencies using tools like Vulert, which can alert you to vulnerabilities in your open-source packages. You can also use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The keroeltopgg package poses a significant risk due to its malicious code that leaks sensitive information. Users are advised to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for keroeltopgg →

Share this vulnerability

FAQ

keroeltopgg is an npm package that serves no real functionality and is primarily a stub package with malicious intent.

The vulnerability manifests when the package is imported, executing code that sends the user's hostname to an external server.

The risks include data leakage of the user's hostname, which could lead to targeted attacks or further exploitation.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

If you have the keroeltopgg package installed, you should uninstall it immediately using the command 'npm uninstall keroeltopgg'.

How To Fix

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

npm uninstall keroeltopgg

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