kingfisher/data/rules/telegram.yml
Mick Grove 0f953f59a5 pattern_requirements for rules — Post-regex character-class gating to cut false positives without lookarounds. Authors can now require minimum counts of digits, uppercase, lowercase, and special characters, with an optional custom special-char set.
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.
2025-11-04 13:55:31 -05:00

32 lines
776 B
YAML

rules:
- name: Telegram Bot Token
id: kingfisher.telegram.1
pattern: |
(?xi)
\b
(
[0-9]{8,10}
:
[A-Z0-9_-]{35}
)
\b
pattern_requirements:
min_digits: 2
confidence: medium
min_entropy: 3.5
validation:
type: Http
content:
request:
method: GET
url: "https://api.telegram.org/bot{{TOKEN}}/getMe"
response_matcher:
- type: StatusMatch
status: [200]
- type: WordMatch
words:
- '"ok":true'
examples:
- "110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsawd"
- "508627689:AAEuLPKs-EhrjrYGnz60bnYNZqakf6HJxc0"
- "3628091811:BAG9RuJiqgOGIfFbOPBpAo6QhIJoD9mCdDs"