Flagged months before it woke up
This is a div block with a Webflow interaction that will be triggered when the heading is in the view.

Most security metrics still start when something is already loud: a detection, a ticket, a customer complaint. This batch started when the domains were quiet.
The sequence
Bought in bulk. On 24 September 2025, 25 domains were registered on the same day through one registrar and delegated to badgerdns, inside the traffic-machine nameserver family. Most are random seven-letter .com names (djcxtew[.]com, fmwesgr[.]com, kyyepzh[.]com). Others read like lures: ibanking-dbs-verify[.]com, mygovaufunds[.]com, vz-help[.]com.
Flagged early. Malanta classified most of them as malicious between 30 November and 15 December 2025, about ten weeks after registration. Several names were already known to Malanta from earlier registrations in 2023.
Left to sit. They stayed parked on the operator's addresses for about eight months.
Switched on together. In the week of 23 August 2026, Quad9 lookups for the batch (shared with Malanta for domains on Malanta's indicator list) jumped to about seven times those of comparable domains on the same nameserver domain and ending. The elevation held about three weeks, then fell back by late September.
Random strings do not attract mistyped traffic on their own. Something referred to these names together during those weeks: spam, links, bots, or scanning. DNS telemetry shows timing, not purpose. High confidence for the pattern. Low-Medium for the cause.
Why this is an IoPA story
Indicators of Compromise describe resources after they are useful to an attack. Indicators of Pre-Attack describe resources while they are still being held, aged, or wired.
These 25 names were on Malanta's list eight to nine months before the burst. That is lead time. We did not compute a Mean Time to Preempt for this case, and we did not invent a savings figure. We recorded the order: register, flag, park, then simultaneous use.
The durable context is the same platform in Blog 0: about 115,000 fronts, every sector, visitors screened and sold. Staging inventory and live monetization share nameservers.
What programs should measure instead
Suggested operational metrics from the technical report (no measured values claimed here):
- New family members per week (growth and churn of the front layer)
- Time from first delegation to policy coverage
- Outcome difference by visitor profile (how much a single-profile check misses)
- User exposures via the family (resolver hits per user and per typo)
The strategic shift for leadership is simple. Readiness includes whether staging infrastructure was visible early enough to act, not only whether last week's lure was blocked.
The Bottom Line
Idle on a known malicious nameserver family is not the same as harmless. A traffic burst that arrives together after months of quiet is what a setup window looks like in DNS. Sector-scoped feeds that wait for a campaign label will keep arriving after the inventory is already paid for.
Full Quad9 timeline and indicator CSV: technical report. For a board-ready cut of the same research, use the CISO Executive Summary published with this series.
Pre-Attack Prevention. Hit the source.








