forked from mirrors/kingfisher
0f953f59a5
Why: Hyperscan doesn’t support lookaheads/behinds, so many “must contain X and Y” checks had to be baked into the regex (hurting readability) or were impossible. pattern_requirements applies lightweight, in-memory checks after a match is found, keeping patterns fast and clean.
38 lines
No EOL
1.1 KiB
YAML
38 lines
No EOL
1.1 KiB
YAML
rules:
|
|
- name: Apify API Token
|
|
id: kingfisher.apify.1
|
|
pattern: |
|
|
(?xi)
|
|
(
|
|
apify_api_[A-Z0-9]{34,38}
|
|
)
|
|
\b
|
|
pattern_requirements:
|
|
min_digits: 2
|
|
min_uppercase: 1
|
|
min_lowercase: 1
|
|
confidence: medium
|
|
min_entropy: 3.5
|
|
validation:
|
|
type: Http
|
|
content:
|
|
request:
|
|
method: GET
|
|
url: "https://api.apify.com/v2/users/me"
|
|
headers:
|
|
Authorization: "Bearer {{ TOKEN }}"
|
|
response_matcher:
|
|
- type: StatusMatch
|
|
status: [200]
|
|
- type: WordMatch
|
|
words:
|
|
- '"data"'
|
|
- '"username"'
|
|
match_all_words: true
|
|
references:
|
|
- https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/apify_token
|
|
- https://docs.apify.com/api/v2#/reference/users/user-object/get-user-public-profile-or-me
|
|
- https://docs.apify.com/api/v2/users-me-get
|
|
examples:
|
|
- "apify_api_NcjXcxEz2XL1irjppyWSHvjghalQOd1LXOHv"
|
|
- "apify_api_9uyewBxQUF1EXWdKVc4lNaTSM461Ls4oQouz" |