IntelOwl accepts indicators, runs analyzers and connectors, and returns intelligence through a single API. Its stored jobs can reveal what an organization is investigating, and its connector configuration can hold access to external intelligence services. A public instance is therefore both an analysis tool and a concentration of sensitive context.

Observation

At 07:50 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="IntelOwl" returned 0 matches. title="IntelOwl" returned 6,669 matches.

The large title population requires stronger interpretation than a simple exposure estimate. Project documentation, public demos, tutorials, and unrelated pages may share the name. Even if only a small fraction are real consoles, the count is high enough to justify a repeatable ownership and access review process.

Identity, jobs, and connectors

IntelOwl's usage documentation says server authentication is managed by API tokens. The API documentation says job deletion or termination is limited to the owner or another user in the same organization. That makes organization membership and job ownership useful review dimensions.

For each verified installation, inventory users, organizations, API tokens, analyzer visibility, connector credentials, and retention of submitted indicators. A user who can create jobs may cause external lookups and store provider responses. A user who can change plugin configuration may alter how future sensitive data is processed.

Review whether privacy-sensitive analyzers are enabled, whether job results can be downloaded, and whether a token belongs to a person or a long-running integration. API tokens created for scripts should have a named owner, purpose, creation date, and revocation path.

Operational checks

  • Confirm that the API and web interface require authentication.

  • Review organization boundaries and job visibility.

  • Inventory external service keys and their source.

  • Test deletion by an unrelated user and by a same-organization user.

  • Confirm log retention for submitted indicators and downloaded results.

  • Check whether public documentation or demo titles are being counted as production leads.

ZoomEye gives a bounded view of title matches at a known time. It does not reveal token scope, organization membership, or whether a candidate is actually running IntelOwl. The value is in using the observation to drive a precise inventory rather than treating 6,669 as a vulnerability count.

References