Jul 20, 2015 09:06 PM
(This post was last modified: Jul 21, 2015 01:03 AM by QU⚡CKSILVER.)
Today I found out that DuckDNS owners/admins had taken control over a subdomain that I registered on there a year ago.. It had been working ever since and many of my clients are still resolving this subdomain, but guess what? DuckDNS has taken control over my subdomain now for an unknown reason. (I assume it is to check if it's being used for a botnet... Don't know to be honest).
How it all started? Well, basically, my DuckDNS updater had problems updating the subdomain and it was showing the following error:
![[Image: f98a50c9b5404ba52fd6962974b1b1da.png]](https://i.gyazo.com/f98a50c9b5404ba52fd6962974b1b1da.png)
Okay then... I was wondering why it was happening, so I managed to go to DuckDNS site and surprisingly saw that the registered subdomain was not in the list (deleted)... I tried to add it again, but Oh... BIG SURPRISE. Just look below, lol.
![[Image: 2277e133eda423098b32051b4529b6bf.png]](https://i.gyazo.com/2277e133eda423098b32051b4529b6bf.png)
After seeing this crap, I was like ''What the heck, how is that even possible? Why would I delete my own subdomain? How come it is now taken by another user?''
Before judging this situation as a TAKEOVER from DuckDNS admins, I managed to resolve the domain above to find out if it was still alive, where it is now pointing to and perform a port scan on it.
Turns out the domain is now pointing to: 192.169.69.25 and it has the port 80 open.
IPWHOIS:![[Image: b7ba70be3e568ef0a1ca38060376d510.png]](https://i.gyazo.com/b7ba70be3e568ef0a1ca38060376d510.png)
When I saw the port 80 was open, I knew it had to be a webserver running on that IP address and of course, I opened a new tab and went to http://labrechadera.duckdns.org/ just for curiosity and GUYS, what you're going to see will make you stop using DuckDNS immediately...
![[Image: bd99d96ba010a640c206ff0e631e766f.png]](https://i.gyazo.com/bd99d96ba010a640c206ff0e631e766f.png)
Okay, so I guess this is definetely telling me everything I wanted to know... ''Modern Honeypot Network Server''
More info on ThreatStream and their ''Modern Honeynet Framework'' project here: Spoiler (Click to View)
DuckDNS is no longer safe for RATs/botnets. BEWARE!! If you still don't trust me, you can just do an HTTP request on the IP mentioned above (which is where my subdomain is currently pointing to) and see it for yourself.
To make a long story short, my subdomain (labrechadera.duckdns.org) was basically taken down by DuckDNS administrators because they want to find out if I was using it for malicious purposes (technically I was) but all I can say is to stop using DuckDNS for Remote Administration Tools/Botnets, as you could be surprised someday.
How it all started? Well, basically, my DuckDNS updater had problems updating the subdomain and it was showing the following error:
![[Image: f98a50c9b5404ba52fd6962974b1b1da.png]](https://i.gyazo.com/f98a50c9b5404ba52fd6962974b1b1da.png)
Okay then... I was wondering why it was happening, so I managed to go to DuckDNS site and surprisingly saw that the registered subdomain was not in the list (deleted)... I tried to add it again, but Oh... BIG SURPRISE. Just look below, lol.
![[Image: 2277e133eda423098b32051b4529b6bf.png]](https://i.gyazo.com/2277e133eda423098b32051b4529b6bf.png)
After seeing this crap, I was like ''What the heck, how is that even possible? Why would I delete my own subdomain? How come it is now taken by another user?''
Before judging this situation as a TAKEOVER from DuckDNS admins, I managed to resolve the domain above to find out if it was still alive, where it is now pointing to and perform a port scan on it.
Turns out the domain is now pointing to: 192.169.69.25 and it has the port 80 open.
IPWHOIS:
![[Image: b7ba70be3e568ef0a1ca38060376d510.png]](https://i.gyazo.com/b7ba70be3e568ef0a1ca38060376d510.png)
When I saw the port 80 was open, I knew it had to be a webserver running on that IP address and of course, I opened a new tab and went to http://labrechadera.duckdns.org/ just for curiosity and GUYS, what you're going to see will make you stop using DuckDNS immediately...
![[Image: bd99d96ba010a640c206ff0e631e766f.png]](https://i.gyazo.com/bd99d96ba010a640c206ff0e631e766f.png)
Okay, so I guess this is definetely telling me everything I wanted to know... ''Modern Honeypot Network Server''
More info on ThreatStream and their ''Modern Honeynet Framework'' project here: Spoiler (Click to View)
DuckDNS is no longer safe for RATs/botnets. BEWARE!! If you still don't trust me, you can just do an HTTP request on the IP mentioned above (which is where my subdomain is currently pointing to) and see it for yourself.
To make a long story short, my subdomain (labrechadera.duckdns.org) was basically taken down by DuckDNS administrators because they want to find out if I was using it for malicious purposes (technically I was) but all I can say is to stop using DuckDNS for Remote Administration Tools/Botnets, as you could be surprised someday.




![[Image: tIUCpQ.gif]](https://vgy.me/tIUCpQ.gif)