The Moroccan Court Summons

This is mass-blast garbage, not a targeted incident. Thousands of Texans got the same message today from the same source. I'm logging it here for the texture, not because it represents anything specific about my situation — and to use it as a small worked example of the kind of filter discipline a targeted person has to do at higher volume than they would otherwise.

Multiple individually-conclusive tells, any one of which is enough on its own.

The sender number begins with +212. That's Morocco. A Texas court does not text from a Moroccan phone number. The geography of the sender is the first and cleanest tell — it requires no expertise to verify, just the willingness to look at the country code.

The link points to `tx.dmvcpw.sbs/dmv`. The `.sbs` TLD is one of the cheapest domain extensions available, costs about a dollar a year, and is presently dominated by phishing and scam operations. Real Texas government URLs end in `.tx.gov`. The `tx.[garbage].sbs/dmv` shape is the standard "looks like a state subdomain to a hurried eye" deception template — it's structured to be skimmed past, not read.

Texas District Courts do not handle traffic violations. In Texas, traffic citations go through Justice of the Peace or Municipal courts. District Courts handle felonies and civil cases above a dollar threshold. A real Texas court clerk would never write "Texas District Court – Traffic Violation Summons" because the category is impossible. A foreign scammer working from a template doesn't know this. This is the kind of category error that makes the whole construction collapse at first inspection.

The supporting tells are the kind of fabricated specificity that fills out a phishing template — invented officer names, an invented badge format (Texas has no statewide "TX-" badge numbering scheme), an invented judge, an invented clerk, an invented case-number format. These details are the texture the message hopes will substitute for legitimacy. They look reassuring from a distance and dissolve up close.

The threat stack at the bottom — "arrest warrant, suspension of driving privileges, vehicle impoundment, civil litigation, wage garnishment, and seizure of personal assets without notice" — is the scam's pressure mechanism. Real court notices specify one consequence with one deadline. Stacked consequences are a fear-pressure pattern, not a legal one.

The "Reply 'G' to receive this summons again" hook is itself a small piece of the operation. Replies do two things: they confirm the number is live, raising the recipient's value as a future target, and on some carriers they whitelist the sender for follow-up messages that would otherwise be filtered. Replying to confirm or deny is the response a hurried person produces; the correct response is no response, plus reporting through the spam channels Apple already offered (and the universal carrier shortcode 7726).

For a moment of independent corroboration: iMessage itself had already flagged the sender. The second screenshot shows the "If you did not expect this message from an unknown sender, it may be junk. Report Spam" banner Apple attaches to senders its anti-spam classifier doesn't trust. That banner is the easiest single tell of all — the platform is telling you it doesn't trust the source before you even read the body.

The reason to write this one up is not that it represents anything about my situation. It's that the ocean of obvious mass-blast garbage is the medium through which any actually-pointed message would also arrive. The filter discipline that catches the obvious ones cleanly is the same filter discipline that has to remain calibrated for the rare message that needs different attention. Burning the filter on the easy ones — getting nervous, replying, clicking, calling the supposed agency — degrades the filter for the harder ones.

The cane stayed in the corner. The phone stayed in my hand. The link did not get tapped. The "Report Spam" got tapped. On to the rest of the afternoon — a new piece going up at spiritb.com.