A fully-permissive wildcard appears in better-auth's trustedOrigins.
Why AI tools produce this: AI coding tools produce this regularly, typically when prompted for a shortcut or a quick fix.
Why this matters
trustedOrigins is better-auth's origin allow-list for CSRF and callback protection. An entry of "*", "**", or a protocol-only wildcard like "https://*" / "*://*" matches EVERY host, so any website can drive authenticated cross-origin requests and receive OAuth callbacks. This defeats the origin check entirely (CWE-942 / CWE-352).
List the exact origins you trust instead: trustedOrigins: ["https://app.example.com"]. A scoped subdomain wildcard ("https://*.example.com") is fine; a bare or protocol-only * is not.
Suppressing this rule
If a finding is a genuine false positive, scope the suppression to the exact line and leave a reason, never disable the rule project-wide. Disable directives are line-scoped by design.
// oauthlint-disable-next-line auth.betterauth.trusted-origins-wildcard -- <reason>