One NanoMQ title match still points to an MQTT and HTTP control plane
A small internet count can describe a narrow fingerprint rather than a harmless service. NanoMQ is a lightweight MQTT broker with authentication, access-control, and HTTP API options. A count-only ZoomEye probe found one asset with title="NanoMQ" and zero with app="NanoMQ". The result is too small for a population claim, but it is enough to show why broker management paths deserve a separate review.
NanoMQ documents user-login authorization, access control lists, and HTTP authorization. Its HTTP server configuration includes a listening port, connection limit, authentication type, and a JWT public-key file. The HTTP API V4 documentation says the API uses Basic Authentication or JWT Authentication and can query brokers, clients, and subscriptions, as well as publish messages or reload configuration.
What the count covers
The two ZoomEye SDK queries used app="NanoMQ" and title="NanoMQ" with sub_type="all", page 1, and page size 1 at 08:42 Asia/Shanghai on 17 November 2026. The application query returned 0 and the title query returned 1. These totals describe matches for those exact fields. They do not measure MQTT listeners that do not display the product name, brokers behind a reverse proxy, or deployments reached over private networks.
A title-only result can be a dashboard entry page or an unauthenticated error page. It should not be called a vulnerable broker without checking the version and configuration. The same caution applies to a zero application count: this query did not find the fingerprint, and the owner still has to inspect the configured MQTT and HTTP listeners.
Separate the two planes
The MQTT listener carries client identity and publish/subscribe authority. Review username/password storage, JWT validation, HTTP authentication callbacks, and topic ACLs. A client that can subscribe to $SYS/# or a broad wildcard may learn broker and client state. A client that can publish to a wildcard or management topic may affect every device that trusts that namespace.
The HTTP listener can be more powerful than a dashboard. If it exposes publish, client, subscription, or configuration operations, Basic credentials and JWTs need the same secret handling as any administrative API. Bind the HTTP service to a management interface, verify the JWT key file, limit request size and rate, and log changes without recording credentials.
A bounded validation path
Inventory NanoMQ hosts by owner and deployment type. Check whether port 8081 or another HTTP port is reachable from the internet, whether TLS terminates in front of it, and whether Basic authentication is enabled with a unique secret. Test the ACL against a normal sensor identity and an administration identity. Confirm that disabling an account removes both MQTT and HTTP access.
ZoomEye gives one observable candidate in this query. The useful conclusion concerns the broker's control plane, not the size of the population.
Top comments (0)