4 ms·
Additional information and discussion: https://gist.github.com/susam/3cb42e571c4ab12987b286791bdfe9d2 https://gist.github.com/susam/3cb42e571c4ab12987b286791bdf
by zenexer 7y ago
Additional information and discussion: https://gist.github.com/susam/3cb42e571c4ab12987b286791bdfe9d2 https://gist.github.com/susam/3cb42e571c4ab12987b286791bdfe9...
Commenters have speculated that the domain was seized by law enforcement due to participation in a malware campaign. The domain in question may have been used by malware that was phoning home, perhaps because the Linode server hosting it was compromised. This stems from the fact that the domain's new nameservers are Shadowserver's sinkholes:
Name Server: sc-c.sinkhole.shadowserver.org
Name Server: sc-d.sinkhole.shadowserver.org
Name Server: sc-a.sinkhole.shadowserver.org
Name Server: sc-b.sinkhole.shadowserver.org
Edit: When querying the domain in RiskIQ, one of the Linode IP addresses formerly associated is tagged with `emerging_threats` and `kaspersky`. Other domains/subdomains associated with the same IP address have similar tags.
One such domain is MathB.in, which is a public pastebin. It's conceivable that malware was phoning home by creating pastes on that site.
Susam, I don't have much experience recovering domains in this state, but it's conceivable that Namecheap will be able to put you in contact with someone who can help resolve the matter. However, if there's something like a sealed court order involved, you may find that you're stonewalled at first. I don't know if there's any available recourse for this, especially since this appears to be an international effort.
- axaxs 7y agoabsolutely. I recognize those nameservers from my work in a registry, and usually came as a request from a federal agency.
- hsivonen 7y agoAt least as of a couple of years ago, Shadowserver could accuse you of botnet participation on such flimsy evidence that it was way too easy to frame someone else as being a botnet participant. I don't want to give ideas how, but it happened to me. Since then, I've configured my firewalls to block traffic to Shadowserver IPv4 space. I'm more worried about getting framed again than actually getting a botnet infection and not getting notified.