Moltbot, an open-source framework for autonomous agent orchestration, has been found leaking control panel access.
Messaging platform credentials through misconfigured multicast DNS (mDNS) broadcasts, exposing over 1,400 instances globally to reconnaissance and potential takeover.
Widespread operational metadata exposure across Moltbot deployments, revealing internal hostnames, filesystem paths, service ports, and messaging platform identity artifacts before any attacker interaction.
The leakage stems from mDNS broadcasts that inadvertently disclose system-level details to anyone on the same network segment.
Identified 1,487 Moltbot instances broadcasting detailed operational metadata via mDNS on port 5353.
The exposed information includes full machine hostnames, Clawdbot Control interface ports (typically 18789), SSH ports, internal filesystem paths, LAN-visible IP addresses, and operational transport metadata.
Geographic analysis revealed exposure across 53 countries, with heavy concentration in the United States. Infrastructure distribution showed DigitalOcean as the primary hosting provider, followed by AWS and OVH.
Of the discovered instances, 88 had publicly accessible web control panels, with 66 exposing both mDNS and web interfaces simultaneously.
Credential Exposure Through Open Directories
Critical security gaps emerged through open directory listings on exposed web servers.
Several hosts revealed messaging platform identity artifacts including Signal, Telegram, and WhatsApp credential files containing registration secrets, identity keys, and QR pairing material.
These artifacts enable complete agent impersonation and represent high-severity credential leakage.
Exposed files also contained operational logs, cryptographic material, runtime caches, and development tools.
This level of transparency allows adversaries to reconstruct or impersonate the entire agent environment without exploiting vulnerabilities.
Network-Level Reconnaissance Vector
mDNS broadcasts function as both discovery beacons and metadata leak vectors. The protocol, while designed for local-only service discovery, exposes detailed system fingerprints to any host sharing the network segment.
This includes workplace Wi-Fi, coffee shops, co-working spaces, hotel networks, and university networks.
Port diversity analysis revealed inconsistent deployment practices. While port 18789 remains dominant, a wide range of alternative ports were identified.
Researchers also discovered a dedicated honeypot with 25 open ports, suggesting active third-party monitoring and early attacker interest in Moltbot deployments.
The exposure pattern demonstrates deployment hygiene failures rather than software vulnerabilities. Before any authentication attempt or network interaction, Moltbot instances self-announce their internal structure through mDNS.
This operational transparency significantly lowers the barrier to compromise by providing attackers with reconnaissance data without requiring active probing.
Magnify scans identified 635 accessible web control interfaces globally, distributed across major cloud providers and some organizational networks.
The presence of messaging platform credentials in open directories enables adversaries to bypass authentication entirely and assume agent identities for phishing, social engineering, or lateral movement.
The findings reveal recurring configuration failures across the Moltbot ecosystem. Operators frequently deploy instances without understanding mDNS broadcast implications or implementing basic access controls.
The combination of service advertisements, open directories, and credential exposure represents a systemic deployment issue rather than isolated misconfigurations.
Additional research has raised concerns about prompt injection attacks and data security in Moltbot deployments.
The current exposure landscape demonstrates that many instances leak meaningful operational data without any attacker interaction, creating pre-authentication compromise opportunities through metadata alone.
Organizations deploying Moltbot should immediately audit mDNS broadcasts, restrict network-level service advertisements, implement directory access controls, and secure messaging platform credentials.
The exposure patterns indicate that powerful automation frameworks require corresponding security rigor during deployment.
Follow us on Google News , LinkedIn and X to Get More Instant Updates. Set Cyberpress as a Preferred Source in Google.
