# Hunt requests for AI tool files, then check your release directory

Start with the two [Sigma rules](sigma/README.md), using your web server's access logs. For an immediate platform hunt, use the [Microsoft Sentinel / Azure Monitor query](sentinel/README.md), [Splunk search](splunk/README.md), [Sumo Logic search](sumologic/README.md), [Elastic ES|QL hunts](elastic/README.md), or [CrowdStrike CQL hunt](crowdstrike/README.md). To check an unpacked release locally, use the [artifact path inventory](artifact/README.md).

The request rules look for ten selected path endings. They report what a client requested, including failed requests. A match does not establish that the file exists, that a response contained a secret, or that a credential was used. A `200` response may be an application's catch-all page. Review response evidence and the actual release before declaring exposure.

| Check | Input | Result |
| --- | --- | --- |
| Sigma credential request | Web access log request path | Request ending in `/.claude/.credentials.json` |
| Sigma configuration request | Web access log request path | Request for one of nine selected configuration files |
| Sentinel / Splunk | Native access logs, field mappings below | Both path groups, plus a single URL-decode pass |
| Sumo Logic | Collected Apache common/combined access logs | Both path groups; parse original request and decode once |
| Elastic ES\|QL | Nginx integration / ECS web fields | 9.2+ decoded variant; 8.14+ literal-path fallback |
| CrowdStrike CQL | Apache access logs ingested into LogScale / Next-Gen SIEM | Both path groups; parse preserved raw request and decode once |
| Local artifact inventory | Explicit unpacked staging directory | Relative file paths matching the same selected endings |

These are experimental hunt starters. Test your own ingestion and known request before enabling an alert. Local fixtures and a Sigma-to-Splunk backend conversion were checked. New native translations were independently reviewed against vendor documentation and safe fixtures. Native query compilation and vendor/customer-tenant execution were not performed. The native queries are manually authored translations, not backend-generated output.

## Investigate a match

1. Confirm which server received the request, its time, status, and original path. A reverse proxy may be the logged client; establish the actual source before grouping by address.
2. Compare nearby requests on that server and separate approved testing or intentional examples from unexpected discovery.
3. Check the final deployed directory and serving configuration. If needed, have the authorized application owner verify the response body without copying credentials into a ticket or chat.
4. If a real credential was exposed, revoke or rotate it through its provider, investigate relevant use, and fix the deployment boundary. A path request alone does not justify assuming compromise.

## Scope and normalization

All rules accept upper- or lowercase path spelling as a hunting choice even when the server is case-sensitive. Nested deployments are included by matching a slash-prefixed ending. Query-only filename mentions, backup suffixes, trailing slashes, directory-only requests, and other filenames are outside this selected list. Add separately reviewed endings for the tools you actually deploy. The list is a practical subset, not a complete AI-tool inventory or a reproduction of every path in the research.

Sigma matches the supplied path as recorded, with no decoder. Decoded native searches remove a literal query separator before decoding once; the older-version Elastic fallback matches its ingested path without an extra decoding pass. Double encoding, application-specific path rewriting, semicolon parameters, escaped log representations, and prior ingestion decoding can change coverage. Preserve original events and check your server's behavior. Do not repeatedly decode until a string matches.

The CrowdStrike version uses CQL on separately ingested inbound Apache logs in Falcon LogScale or Next-Gen SIEM. It is not an endpoint-only Falcon rule. Sumo Logic uses collected raw Apache access logs; Elastic uses documented Nginx integration fields. Follow each source guide before running the query. No CommonSecurityLog or Sophos endpoint translation is included: endpoint process and network-connection events do not establish inbound URL-path coverage.

The local inventory checks filenames directly. A YARA text marker would neither prove secret content nor identify every configuration, so this pack uses path triage instead. Path results must be assessed against the intended public artifact and access policy; some configuration files are deliberately shared.

See [SOURCES.md](SOURCES.md) for the primary documentation behind fields and selected file locations. [index.json](index.json) lists the distributed files and prerequisites.
