Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. In today's episode of "Can It Run Doom": DNS fucking TXT records.

In today's episode of "Can It Run Doom": DNS fucking TXT records.

Scheduled Pinned Locked Moved Uncategorized
infosecdnsdoomitisalwaysdns
62 Posts 49 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • k3ym0@infosec.exchangeK k3ym0@infosec.exchange

    In today's episode of "Can It Run Doom": DNS fucking TXT records.

    Some absolute madlad (cough Adam Rice cough) compressed the entire shareware DOOM WAD, split it into around 1,964 chunks, shoved them into Cloudflare TXT records, and wrote a PowerShell script that reassembles and runs the whole goddamn game from DNS queries alone. Nothing touches disk. The DLLs are in DNS. THE FUCKING DLLS ARE IN DNS.

    RFC 1035 was written in 1987. Those engineers are spinning in their graves fast enough to generate municipal power.

    Bonus: this is a fully functional globally-distributed covert data exfil channel that your NGFW will never fucking see if you're not doing deep DNS inspection. Sleep well.

    blog: https://blog.rice.is/post/doom-over-dns/

    repo: https://github.com/resumex/doom-over-dns

    Also lmao @ every blue team that has never once looked at their DNS query volume. How's that DLP policy working out for you.

    It was always DNS.

    #infosec #dns #doom #itisalwaysdns

    E This user is from outside of this forum
    E This user is from outside of this forum
    esoteric_programmer@social.stealthy.club
    wrote last edited by
    #49

    @k3ym0 holy shit, awesome! this sounds like a passage from @pluralistic little brother, I can't spoil it any further, but it involves dns

    1 Reply Last reply
    0
    • k3ym0@infosec.exchangeK k3ym0@infosec.exchange

      In today's episode of "Can It Run Doom": DNS fucking TXT records.

      Some absolute madlad (cough Adam Rice cough) compressed the entire shareware DOOM WAD, split it into around 1,964 chunks, shoved them into Cloudflare TXT records, and wrote a PowerShell script that reassembles and runs the whole goddamn game from DNS queries alone. Nothing touches disk. The DLLs are in DNS. THE FUCKING DLLS ARE IN DNS.

      RFC 1035 was written in 1987. Those engineers are spinning in their graves fast enough to generate municipal power.

      Bonus: this is a fully functional globally-distributed covert data exfil channel that your NGFW will never fucking see if you're not doing deep DNS inspection. Sleep well.

      blog: https://blog.rice.is/post/doom-over-dns/

      repo: https://github.com/resumex/doom-over-dns

      Also lmao @ every blue team that has never once looked at their DNS query volume. How's that DLP policy working out for you.

      It was always DNS.

      #infosec #dns #doom #itisalwaysdns

      zymurgic@mastodon.onlineZ This user is from outside of this forum
      zymurgic@mastodon.onlineZ This user is from outside of this forum
      zymurgic@mastodon.online
      wrote last edited by
      #50

      @k3ym0 I did long ago work out that DNS is jolly good at distributing fairly static hierarchical datasets, because it inherently caches. For instance, they were once used to route faxes to appropriate gateways on the old tpc.int email to fax service. I also worked out a postcode to address and postcode geocoding schema.

      1 Reply Last reply
      0
      • flo_rian@norden.socialF flo_rian@norden.social

        @k3ym0
        “Those engineers are spinning in their graves”
        1987 was less than 40 years ago and as far I can tell the author is still alive and active.

        mal3aby@mastodon.smears.orgM This user is from outside of this forum
        mal3aby@mastodon.smears.orgM This user is from outside of this forum
        mal3aby@mastodon.smears.org
        wrote last edited by
        #51

        @Flo_Rian @k3ym0 Yep - first reaction: "Wait, who buried Paul Mockapetris alive?!"

        1 Reply Last reply
        0
        • zaphodb@twitter.resolvt.netZ This user is from outside of this forum
          zaphodb@twitter.resolvt.netZ This user is from outside of this forum
          zaphodb@twitter.resolvt.net
          wrote last edited by
          #52

          @da_667 @DaveMWilburn @k3ym0 .oO( ip6.arpa PTR )

          1 Reply Last reply
          0
          • k3ym0@infosec.exchangeK k3ym0@infosec.exchange

            In today's episode of "Can It Run Doom": DNS fucking TXT records.

            Some absolute madlad (cough Adam Rice cough) compressed the entire shareware DOOM WAD, split it into around 1,964 chunks, shoved them into Cloudflare TXT records, and wrote a PowerShell script that reassembles and runs the whole goddamn game from DNS queries alone. Nothing touches disk. The DLLs are in DNS. THE FUCKING DLLS ARE IN DNS.

            RFC 1035 was written in 1987. Those engineers are spinning in their graves fast enough to generate municipal power.

            Bonus: this is a fully functional globally-distributed covert data exfil channel that your NGFW will never fucking see if you're not doing deep DNS inspection. Sleep well.

            blog: https://blog.rice.is/post/doom-over-dns/

            repo: https://github.com/resumex/doom-over-dns

            Also lmao @ every blue team that has never once looked at their DNS query volume. How's that DLP policy working out for you.

            It was always DNS.

            #infosec #dns #doom #itisalwaysdns

            artemis@climatejustice.socialA This user is from outside of this forum
            artemis@climatejustice.socialA This user is from outside of this forum
            artemis@climatejustice.social
            wrote last edited by
            #53

            @k3ym0 holy shit that is next level 'because I could'. Mad props.

            1 Reply Last reply
            0
            • k3ym0@infosec.exchangeK k3ym0@infosec.exchange

              In today's episode of "Can It Run Doom": DNS fucking TXT records.

              Some absolute madlad (cough Adam Rice cough) compressed the entire shareware DOOM WAD, split it into around 1,964 chunks, shoved them into Cloudflare TXT records, and wrote a PowerShell script that reassembles and runs the whole goddamn game from DNS queries alone. Nothing touches disk. The DLLs are in DNS. THE FUCKING DLLS ARE IN DNS.

              RFC 1035 was written in 1987. Those engineers are spinning in their graves fast enough to generate municipal power.

              Bonus: this is a fully functional globally-distributed covert data exfil channel that your NGFW will never fucking see if you're not doing deep DNS inspection. Sleep well.

              blog: https://blog.rice.is/post/doom-over-dns/

              repo: https://github.com/resumex/doom-over-dns

              Also lmao @ every blue team that has never once looked at their DNS query volume. How's that DLP policy working out for you.

              It was always DNS.

              #infosec #dns #doom #itisalwaysdns

              messieass@procial.tchncs.deM This user is from outside of this forum
              messieass@procial.tchncs.deM This user is from outside of this forum
              messieass@procial.tchncs.de
              wrote last edited by
              #54

              @k3ym0@infosec.exchange
              Ho. Lee. Shit
              Was it already encoded in morse code?
              This clearly HAD to be done, but not by anyone i know.

              1 Reply Last reply
              0
              • k3ym0@infosec.exchangeK k3ym0@infosec.exchange

                @ck0

                Most serious companies don't allow DNS queries to servers outside of their network.

                Oh my sweet, sweet, child. If only this were true. I could name-drop several multi-billion $ enterprise orgs that still don’t do this.

                johntimaeus@infosec.exchangeJ This user is from outside of this forum
                johntimaeus@infosec.exchangeJ This user is from outside of this forum
                johntimaeus@infosec.exchange
                wrote last edited by
                #55

                @k3ym0 @ck0

                Even if they don't allow queries beyond the internal servers. Guess what the internal servers are doing?
                They are relaying the queries and answers.

                1 Reply Last reply
                0
                • da_667@infosec.exchangeD da_667@infosec.exchange

                  @DaveMWilburn @k3ym0 I'm also somewhat aware that, there are some services that use TXT records for validation (SPF), and I've heard that some apple services use them for their messenger programs. I've also seen Sophos doing incredibly dumb things with TXT records, but my point still stands is that if you have any capacity for DNS logs, then shit like this sticks out like a sore thumb.

                  However, I can acknowledge my experiences and yours are two different things. Thats fine. I can be wrong.

                  johntimaeus@infosec.exchangeJ This user is from outside of this forum
                  johntimaeus@infosec.exchangeJ This user is from outside of this forum
                  johntimaeus@infosec.exchange
                  wrote last edited by
                  #56

                  @da_667 @DaveMWilburn @k3ym0

                  DNS logs, a well built forwarding chain, and a properly tuned dashboard will trigger on this in a few hundreds of milliseconds.

                  But how many enterprises have that? We're still trying to convince people that naked RDP on the Internet is a bad idea, and that industrial control systems shouldn't ship with open telnet and default creds.

                  k3ym0@infosec.exchangeK onedawnconstant@climatejustice.socialO 2 Replies Last reply
                  0
                  • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

                    @da_667 @DaveMWilburn @k3ym0

                    DNS logs, a well built forwarding chain, and a properly tuned dashboard will trigger on this in a few hundreds of milliseconds.

                    But how many enterprises have that? We're still trying to convince people that naked RDP on the Internet is a bad idea, and that industrial control systems shouldn't ship with open telnet and default creds.

                    k3ym0@infosec.exchangeK This user is from outside of this forum
                    k3ym0@infosec.exchangeK This user is from outside of this forum
                    k3ym0@infosec.exchange
                    wrote last edited by
                    #57

                    @johntimaeus @da_667 @DaveMWilburn cries

                    1 Reply Last reply
                    0
                    • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

                      @da_667 @DaveMWilburn @k3ym0

                      DNS logs, a well built forwarding chain, and a properly tuned dashboard will trigger on this in a few hundreds of milliseconds.

                      But how many enterprises have that? We're still trying to convince people that naked RDP on the Internet is a bad idea, and that industrial control systems shouldn't ship with open telnet and default creds.

                      onedawnconstant@climatejustice.socialO This user is from outside of this forum
                      onedawnconstant@climatejustice.socialO This user is from outside of this forum
                      onedawnconstant@climatejustice.social
                      wrote last edited by
                      #58

                      @johntimaeus @da_667 @DaveMWilburn @k3ym0
                      Industrial controls? They're still shipping household routers with open telnet. Thanks, TP-Link!

                      da_667@infosec.exchangeD johntimaeus@infosec.exchangeJ 2 Replies Last reply
                      0
                      • onedawnconstant@climatejustice.socialO onedawnconstant@climatejustice.social

                        @johntimaeus @da_667 @DaveMWilburn @k3ym0
                        Industrial controls? They're still shipping household routers with open telnet. Thanks, TP-Link!

                        da_667@infosec.exchangeD This user is from outside of this forum
                        da_667@infosec.exchangeD This user is from outside of this forum
                        da_667@infosec.exchange
                        wrote last edited by
                        #59

                        @onedawnconstant @johntimaeus @DaveMWilburn @k3ym0 ONE DAY, LONG AFTER I PASS, THEY WILL SUMMON ME WITH A D-LINK ROUTER AND CHILI FRIES WITH MUSTARD IN A SUMMONING CIRCLE. I WILL RUN IOT_HUNTER ONCE, AND GO BACK TO CRYPT-SLEEP.

                        1 Reply Last reply
                        0
                        • onedawnconstant@climatejustice.socialO onedawnconstant@climatejustice.social

                          @johntimaeus @da_667 @DaveMWilburn @k3ym0
                          Industrial controls? They're still shipping household routers with open telnet. Thanks, TP-Link!

                          johntimaeus@infosec.exchangeJ This user is from outside of this forum
                          johntimaeus@infosec.exchangeJ This user is from outside of this forum
                          johntimaeus@infosec.exchange
                          wrote last edited by
                          #60

                          @onedawnconstant @da_667 @DaveMWilburn @k3ym0

                          Home routers can't (directly (usually)) cause a failure that blows up a gas pipeline, drop a grid, or simply quit monitoring the particulate ratio at the top of a grain silo.

                          onedawnconstant@climatejustice.socialO 1 Reply Last reply
                          0
                          • johntimaeus@infosec.exchangeJ johntimaeus@infosec.exchange

                            @onedawnconstant @da_667 @DaveMWilburn @k3ym0

                            Home routers can't (directly (usually)) cause a failure that blows up a gas pipeline, drop a grid, or simply quit monitoring the particulate ratio at the top of a grain silo.

                            onedawnconstant@climatejustice.socialO This user is from outside of this forum
                            onedawnconstant@climatejustice.socialO This user is from outside of this forum
                            onedawnconstant@climatejustice.social
                            wrote last edited by
                            #61

                            @johntimaeus @da_667 @DaveMWilburn @k3ym0

                            Not directly, but 300 of them in the default configuration can easily allow for infrastructure attacks through botnets, spearphishing, etc. Smear that stuff around and somethings bound to go wrong.

                            Someone always has something they shouldn't, and that's how stuff croaks.

                            1 Reply Last reply
                            0
                            • da_667@infosec.exchangeD da_667@infosec.exchange

                              @DaveMWilburn @k3ym0 I'm well aware that trying to base your detection on shannon entropy is an exercise in futility, as most cloud providers have the "malware to ops DGA that looks like its very malicious" down pat. But I will still say, if you suddenly are getting assloads of TXT records with the same domain in common, so long as you have DNS logs at all, you can probably do some form of statistical analysis and notice that this number of DNS TXT records from one place looks really fucking jank.

                              jornane@ipv6.socialJ This user is from outside of this forum
                              jornane@ipv6.socialJ This user is from outside of this forum
                              jornane@ipv6.social
                              wrote last edited by
                              #62

                              @da_667 @DaveMWilburn @k3ym0 If I wanted to avoid detection, I’d send the information in AAAA records, not TXT.

                              1 Reply Last reply
                              0
                              • R relay@relay.infosec.exchange shared this topic
                              Reply
                              • Reply as topic
                              Log in to reply
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes


                              • Login

                              • Login or register to search.
                              • First post
                                Last post
                              0
                              • Categories
                              • Recent
                              • Tags
                              • Popular
                              • World
                              • Users
                              • Groups