Weekly threat-intel roadmap — 2026-07-26 - #107
Open
alekslinde wants to merge 2 commits into
Open
Conversation
Six new detection gaps identified: high-abuse TLD escalation (.shop/.store/.vip/.lol/.monster promoted from watchlist), TOAD callback phishing via fake subscription email (Norton/McAfee/Geek Squad/Coinbase), Chinese authority/foreign official impersonation targeting AU diaspora, named ASIC-warned AI trading platforms (Quantum AI / Immediate Edge family), rental-bond "updated bank details" fraud, and myID forced re-registration phishing phrases. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012kuU7cuqbW1DNWnbxrEZDt
Adds a Status block marking D1-D6 as shipped (#101-#106 via #109 and #111), leaving D7 as the sole outstanding item, now tracked in #113. Also records the two places the implementation deviated from the proposals, so this file isn't misread as a description of the shipped code: - D3 went into a separate foreignAuthorityMentions list at +35, not govMentions, whose flag wording ('verify via official channels') is wrong advice for a foreign police impersonation. - D5 kept 'rental bond'/'holding deposit' out of REQUEST_WORDS; they only appear in the composite, matching this file's own note that rental bond alone should not score. Corrects T7/D7: tested against the live regex, 'scan the QR code in the attached PDF' is already caught, so that proposed pattern is redundant. Only the inverted 'the attachment contains a QR code' phrasing is a real gap. Research content is otherwise unchanged. Rebased onto main (was 27 commits behind); docs-only, no code touched.
alekslinde
force-pushed
the
threat-intel/2026-07-26
branch
from
August 2, 2026 13:22
5d31e2c to
129a470
Compare
alekslinde
marked this pull request as ready for review
August 2, 2026 13:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Six new detection gaps identified this week. All proposals are additive-only changes to existing constants/functions in
lib/scamDetector.ts— no architecture changes required..shop,.store,.vip,.lol,.monstertoSUSPICIOUS_TLDSscamDetector.tsscamDetector.tsgovMentions/URGENCY_WORDSscamDetector.tsscamDetector.tsscamDetector.tsscamDetector.tsTop recommendation
#102 (TOAD callback phishing) is the single highest-impact change. Fake subscription emails with no URL currently score too low to warn users, because all existing URL-scanner logic is bypassed. The compound four-factor check (fake brand + call-to-dispute + dollar amount + no URL) is low-FP and catches a Scamwatch-alerted active campaign.
This PR contains
docs/threat-intel/2026-07-26-threat-roadmap.md— research, gap analysis, and full issue bodiesNo
lib/files are modified. Detection changes ship via the individual issues above.