HyperDX API keys put observability access behind a team boundary
HyperDX API keys put observability access behind a team boundary HyperDX is an observability platform for logs, metrics, traces, and session replays. Its team settings hold API access keys, and the project's MCP docume
HyperDX API keys put observability access behind a team boundary
HyperDX is an observability platform for logs, metrics, traces, and session replays. Its team settings hold API access keys, and the project's MCP documentation describes Bearer token authentication for an agent-facing endpoint. A HyperDX instance can therefore hold two kinds of sensitive authority: the telemetry it stores and the tokens that can query or manage that telemetry.
A count-only ZoomEye probe on 18 November 2026 used page 1, one result per page, and sub_type=all. app="HyperDX" returned 0, title="HyperDX" returned 157, and http.body="HyperDX" returned 656. These are field matches. They do not show how many production teams use the software, and they do not prove that an API key is exposed.
Separate ingestion from management
Telemetry ingestion and management access have different risk. An ingestion key that only writes logs is not equivalent to a personal key that can query dashboards, modify alerts, or use the MCP server. The HyperDX documentation distinguishes a personal API access key used for the external API and MCP from the credential used to send OTLP data. Inventory those credentials separately and record their scope, owner, creation time, expiry, and rotation path.
The project changelog also describes team API keys with descriptions and expiry and the ability to rotate personal access keys. Those features reduce the lifetime problem only when operators use them. A long-lived key generated once at account creation and never rotated remains a durable credential, even if the product now supports replacement.
The 157 title matches are the more focused control-plane population. The 656 body matches include documentation and discussions that mention HyperDX. A query that finds the brand in a page title does not tell whether the API is exposed, whether login is enabled, or whether the instance belongs to an organization.
Review the exposed routes
Confirm the front-end host, API host, ingestion route, and any /api/mcp endpoint. The MCP documentation says not every deployment exposes the backend directly, so use the deployment's actual proxy and route configuration. Put the management API and MCP endpoint behind the same identity and network policy as the team interface.
Review team membership and sign-in. If the instance uses local accounts, enforce individual identities and remove departed users. If it uses OIDC, verify the team and group mapping and test what happens when a user is removed. Check whether a browser session can be reused after removal and whether API keys survive account changes. Those are separate controls.
Audit key usage at the API and proxy layers. Alert on keys used from unexpected networks, queries over unusually long time ranges, new dashboard or alert changes, and calls to the MCP endpoint from hosts that are not registered automation systems. Do not put raw keys in dashboards, alerts, query labels, or support tickets.
Make the count useful
Use ZoomEye to find branded pages outside the central inventory, then verify ownership with approved requests. Record the instance URL, team, authentication mode, API route, MCP exposure, and key owners. A title match without an owner is a lead. A managed service that the platform team already knows about is not a new finding.
Compare observations over time to catch a new deployment or a proxy change. A drop in title matches can reflect a login page with a generic title rather than a shutdown. The analyst should preserve the exact field query and recheck the host before changing the asset ledger.
HyperDX is valuable because it brings operational evidence into one place. That concentration makes key scope and team boundaries part of the security review. The external count identifies candidate services. Key inventory and route checks determine whether the observability plane is controlled.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.