This story was not the easiest one to write, courtesy of Monday being a snow day in which most of my queries went unanswered while my wife and I had to keep our daughter entertained. DNS root-zone supervision is an exceedingly wonky topic; did I keep my explanation of it out of the weeds, or is mine too far above the ground to provide enough understanding of the topic?

WAMU host Kojo Nnamdi, CNET columnist Maggie Reardon and I discussed the changing shape of the wireless market–in particular, T-Mobile’s hanging up on subsidized handset pricing. T-Mo marketing v.p. Andrew Sherrard joined us via phone for part of the show and provided a number I hadn’t seen before: From 10 to 20 percent of its customers now bring their own devices to the carrier.

As it has before, my neighborhood’s mailing list proved to be a fruitful source of Q&A column material–and this time around, my research into a neighbor’s problems getting video off an old MiniDV camcorder involved a house call.

Something looked broken with Web search on my computer yesterday, and it took me only about 18 hours of detours to figure out the problem. To spare you all the trouble of repeating my troubleshooting, here’s how things worked out.

My first thought–both frightened and angry–was that I’d finally gotten hit with a virus like DNSChanger on my own computer. But the same hijacked search happened in another Mac and on the Chromebook I’d just reviewed.

But the router had nothing amiss with its domain-name-server settings. Meanwhile, doing the same search in the browser on an AT&T Android phone (another recent review) didn’t yield any spurious results. Tworeplies on Twitter also suggested this issue might be specific to Internet providers.

My last move before getting distracted by our daughter was to try the same search on other sites. At Bing, the result also got hijacked; at DuckDuckGo, it did not.

This morning, as I was using Safari’s Web Inspector to see if I could get any more insight on the mechanics of the hijack (and take the screengrab you see above), another Twitter reply suggested that it could be an issue with CEA’s installation of WordPress. There is a history of exploits for that popular blogging platform that target incoming referrers from popular sites to send those clicks elsewhere; see, for instance, this Q&A thread.

Sucuri LLC’s malware-checking site didn’t find any malware at CEA’s blog. But when I e-mailed somebody at the Arlington, Va., trade association, they did find a malicious script on the site that’s since been removed. And now, my original search takes me to the right page.

So I guess reporting this counts as this week’s good deed for the Internet… and maybe a start on next weekend’s USA Today column. But before I do that: Have you run into anything like this? Were you able to get it resolved? What else would you like to know about search hijacking?