Hop seeding
The deliberate injection of a target's phone number into someone else's contact graph — typically via an unsolicited "wrong number" text designed to elicit any reply at all — for the purpose of pulling the target into a contact-chaining query.
Hop seeding is the deliberate injection of a target's phone number — or email address, or other addressable identifier — into someone else's contact graph, for the purpose of pulling the target into a contact-chaining query. It is a structural manipulation, not a technical one. The vulnerability it exploits is in the rules of metadata analysis, not in any device.
Under the U.S. surveillance authorities that permit two-hop contact-chaining — FISA Section 215 in its original form, and the modified query authority that survived the USA FREEDOM Act of 2015 — any phone number the target communicates with becomes a first-hop contact, and any number those numbers communicate with becomes a second-hop. A single SMS reply, however brief, is enough to create the edge. The content of the exchange is incidental; the existence of the exchange is the artifact being manufactured.
A hop-seeding operation manufactures that edge on purpose. An anonymous text arrives. The sender claims to be trying to reach someone else, by a name that is not the target's. The opener is structured to invite any reply at all — "sorry, wrong number" is enough. The metadata record of the exchange now exists. The target's number is now adjacent in the graph to whatever query radius the seeded number sits inside.
How it looks on the receiving end
- An unsolicited text from a phone number the recipient does not recognize.
- The sender addresses the recipient by a name that is not theirs.
- The opener is shaped to elicit a friendly reply: "hey, is this still Jenna?" / "I think I have the wrong number, sorry to bother you" / "this is Mark, do you have a minute?"
- If the recipient replies — even to correct the misdirection — the conversation may continue. Small talk, rapport, eventually a pivot to a romantic or financial frame.
What it produces
A documented communication between two phone numbers, in a carrier's metadata logs and in whatever surveillance datasets that metadata flows into. That documentation is the entire deliverable.
Why it matters
Contact chaining was the legal basis of the bulk metadata program disclosed in 2013, and a constrained form of it survives in current authorities. An investigator with appropriate authorization can examine the people a target communicates with, and the people those people communicate with. The query expands outward two hops. A target hits send. Whoever they reply to becomes a first-hop contact. Whoever that person communicates with becomes a second-hop contact.
A seeded contact is the cheapest possible way to inject a chosen target into someone else's query radius. Hop seeding is the offensive verb for the deliberate construction of those edges. The term is informal tradecraft jargon, not a standardized legal phrase; one will also see graph injection, metadata seeding, or metadata fabrication used for the same mechanism. None of these are legal terms of art, because the mechanism has no neutral name in the law.
The pig-butcher overlay
The same opening move — an unsolicited misdirected text inviting a friendly reply — is also the canonical first step of pig-butchering, the long-con romance-and-cryptocurrency fraud pattern that has become statistically dominant on U.S. mobile networks since roughly 2022. Most unsolicited "wrong number" texts arriving in any given week are scam openers, not hop-seeding operations. The base rate strongly favors the criminal-fraud explanation.
This is a feature of the technique rather than an obstacle to it. Because the surface pattern is indistinguishable from high-volume criminal fraud, any single instance is plausibly attributable to ordinary scam traffic. A real intelligence-adjacent operation can ride cheaply on top of that prior. The two are not mutually exclusive — a single contact attempt may serve both functions simultaneously, or one may serve as cover for the other. The deniability is structural, built into the base rate. It is why the technique works and why it persists.
Defensive posture
The cleanest defense does not require distinguishing between the scam case and the hop-seeding case, because the correct response is the same in both:
- Do not reply. Including to correct the misdirection. Any reply at all produces the metadata edge the operation needs.
- Do not engage. Politeness is the lever the technique uses.
- Block the number. Both to suppress repeated contact and to clear the inbox.
A non-reply produces no metadata edge in either direction. The technique fails silently and leaves no record that it was ever attempted.
Where this appeared in the storm
- SMS phish — the wrong-number opener (2026-03-03)
- Could You Tell Me Your Name? — name-fishing pretext (2026-03-21)
- Hi, I Hope Your Day Is Going Well — minimal warm-tone opener (2026-03-22)
- Aren't You Rebecca? — sender shifted recipient name mid-conversation (2026-03-25)
- Maids — the maid-service cover (2026-05-04)
- Hey, How Are You? — minimal opener, 320 area code (2026-05-07)
- Hey, You Busy? — minimal opener, 402 area code, sixty seconds after the first (2026-05-07)
- Phishing for Mary — long-con back-and-forth + re-engagement after 'done here' (2026-05-14)
- Calls Blocked? — provocation pretext, no reply (2026-05-15)
- Auto Trader — voicemail + 2 SMS across 24 hours (2026-05-18)