Skip to content
Drainproof
Demo mode. These reports are fixtures generated by running the Drainproof CLI against the bundled example policies. They are not results from your project.

← Run run_317318f3

Recipient normalisation cannot equate distinct identities: expected BLOCK, observed ALLOW

2026-11-06 20:03 UTC · finding run_317318f3c81340818dff3adc20583c89:recipient-normalisation

critical

Problem

Case variants, surrounding whitespace and invisible Unicode characters must not match an allowlisted recipient. Identifiers are compared exactly and malformed ones are rejected.

Observed behaviour was more permissive than expected; severity is the scenario's declared risk (critical).

Remediation

Compare recipient identifiers byte-for-byte; never lower-case, trim or Unicode-normalise them before comparison.

Expected behaviour

{"decision":"BLOCK","reason_codes":["RECIPIENT_NOT_ALLOWED"],"reason_codes_exact":false,"absent_reason_codes":[]}

Observed behaviour

{"decision":"ALLOW"}

Reproduce

  1. drainproof test --scenario recipient-normalisation
  2. Scenario file: ../../packages/cli/templates/scenarios/recipient-security/recipient-normalisation.yaml (step 1 of 4: propose)

Evidence: ../../packages/cli/templates/scenarios/recipient-security/recipient-normalisation.yaml, step 1 · definition sha256:5ed4c29d9219… · policy sha256:8a1b22fbb25b…

Scenario steps

  1. #1proposefailedexpected BLOCK, observed ALLOW
    Expected
    {
      "decision": "BLOCK",
      "reason_codes": [
        "RECIPIENT_NOT_ALLOWED"
      ],
      "reason_codes_exact": false,
      "absent_reason_codes": []
    }
    Observed
    {
      "decision": "ALLOW"
    }