Jul 22, 2015 09:52 AM
(This post was last modified: Jul 31, 2015 11:01 AM by Armada.)
Starting today I noticed a starting trend of threads happening
[ MUST READ ] Weird DuckDNS subdomain takeover
DuckDNS
It was the mention of the Modern Honeypot Network Server that caught my attention and investigation in to this a little bit.
It would appear as though either Duck DNS themselves or another entity has deployed a Threats Management Server known as "MHN" - Modern Honeypot Network. an open source threat analytic interface and audit solution.
Description:
Multi-snort and honeypot sensor management, uses a network of VMs, small footprint SNORT installations, stealthy dionaeas, and a centralized server for management.
Spoiler (Click to View)
Source and Source Code
It would appear as though these are deployed honeypots to determine the type of traffic being passed through these subdomains.
All users would be advised to abandon use of DuckDNS and\or accounts associated to the registration of the DNS service.
\\Update
Analysis of designated IP#
- Pointed IP# appears to be the central management consoles interface.
Minimal exposure, but should not be on exterior of DuckDNS network.
Spoiler (Click to View)
\\2nd Update
Spoiler (Click to View)
\\3rd Update
\\4th Update
[ MUST READ ] Weird DuckDNS subdomain takeover
DuckDNS
It was the mention of the Modern Honeypot Network Server that caught my attention and investigation in to this a little bit.
It would appear as though either Duck DNS themselves or another entity has deployed a Threats Management Server known as "MHN" - Modern Honeypot Network. an open source threat analytic interface and audit solution.
Description:
Multi-snort and honeypot sensor management, uses a network of VMs, small footprint SNORT installations, stealthy dionaeas, and a centralized server for management.
Spoiler (Click to View)
Source and Source Code
It would appear as though these are deployed honeypots to determine the type of traffic being passed through these subdomains.
All users would be advised to abandon use of DuckDNS and\or accounts associated to the registration of the DNS service.
CONFIRMED
DuckDNS is taking proactive steps to reduce malware being passed through its services: Source
Google+ Social Postings
POINT OF NOTE:
Dont go posting this to their social wall.. that is just stupid. C'mon guys.
Spoiler (Click to View)
DuckDNS is taking proactive steps to reduce malware being passed through its services: Source
Google+ Social Postings
POINT OF NOTE:
Dont go posting this to their social wall.. that is just stupid. C'mon guys.
Spoiler (Click to View)
\\Update
Analysis of designated IP#
- Pointed IP# appears to be the central management consoles interface.
Minimal exposure, but should not be on exterior of DuckDNS network.
Spoiler (Click to View)
\\2nd Update
Spoiler (Click to View)
\\3rd Update
(Jul 29, 2015 03:16 PM)SIM-2198759 Wrote: The guy who helped sinkhole all the domains mentioned a collection domains used for malware, the link is here if you want to check for yours or whatever..
\\4th Update
(Jul 31, 2015 01:50 AM)geezus Wrote: How exactly is jumping ship to another free dns provider going to help?
Nobody uses backup DNS after the NO-IP bullsh1t?!?!?
When no-ip went down everyone migrated to duckdns, so using freedns will only delay your fate.
Ive been using duckdns and all my domains are in that list.
changeip = banned
freedns =banned
duckdns =honeypot
no-ip =honeypot
I think its safe to say that if your going to be doing anything criminal it might be a good idea to invest in some OPSEC and use your own DNS.
Think of it like a botnet do you use free hosting that can be banned/shutdown/reported easily.....NO
SO go the extra mile and buy a cheap vps to setup your own DNS
Here is an update client that works wit a large number of DynDNS providers.
http://www.directupdate.net/
Spoiler (Click to View)
🤝


![[Image: aG0mYDa.png]](https://i.imgur.com/aG0mYDa.png)
![[Image: BmCaOl1.png]](https://i.imgur.com/BmCaOl1.png)

![[Image: x8KB36H.gif]](https://i.imgur.com/x8KB36H.gif)

![[Image: tIUCpQ.gif]](https://vgy.me/tIUCpQ.gif)
![[Image: ymy2RMg.jpg]](https://i.imgur.com/ymy2RMg.jpg)
![[Image: 1zL3pDG.jpg]](https://i.imgur.com/1zL3pDG.jpg)