Font file string intepreted as Drupal Hash

Describe the bug

False Positive:

Requires Passive Scanning Alpha in order to have the "Information Disclosure - Drupal Hash (Passive 100010).
A woff2 font file (and by extent, other files too?) content may contains strings that would trigger the regex
https://github.com/zaproxy/community-scripts/blob/bf5135a7cd2ebf9994e28ae354a49633c40abd6c/passive/Find%20Hashes.js#L60

Here is what triggered this regex in my case : $½$u°+ºº¥nu÷{ûJ0»2¼ó¬$Ӗ„—ë¾}'d>æüºJV•õmMdŽÒ
…öVU<
As far as I know Drupal hashes are alphanumeric only.
Maybe a more restrictive regex like some others in the same file could do the job.

Steps to reproduce the behavior

1. Have ZAP passive scan analyze a response with the content of a woff2 font file.
2. If the file happens to contain a string starting with $ followed by a char, then another $ , and whatever 52 other char then the request is going to be tagged as "Information Disclosure - Drupal Hash".

Expected behavior

As the content of a font file has nothing to do with a Drupal hash, this alert should not be raised.

Software versions

ZAP 2.15.0 Desktop

Screenshots

No response

Errors from the zap.log file

No response

Additional context

Passive Scanner Alpha v42.0.0

Would you like to help fix this issue?

• Yes

Start at passive/Find Hashes.js around line 60, where the Drupal hash detection regex is defined. Review how the pattern matches response content, then verify that a woff2 response no longer triggers the alert while valid Drupal hashes still do; the issue does not name a test file.