Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Blocking Ransomware download Domains

    Firewalling
    6
    11
    2.5k
    Loading More Posts
    • 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.
    • T
      tibbs
      last edited by

      Just read about the new ransomware 'PetrWrap'. Article saying that blocking domain 'french-cooking.com' prevents the malicious code in mail attachements to download additional code (doing the encrypt).

      What is the best practice to block domains like this? Sure SquidGuard is not suitable because there is no http traffic in this case.

      Should i block this with firewall rule? But the IP behind 'french-cooking' domain is changing fast.

      About malware domain blacklists. Which one is the best? But also these are good only for http traffic (squidguard) so cannot give protection against any other download method than http? Or can they be integrated into the firewall somehow?

      So what is the best way? Thanks!

      1 Reply Last reply Reply Quote 0
      • T
        tibbs
        last edited by

        Using the DNS forwarder with domain override will do the job? Is it a proper way?
        https://ejnetwork.wordpress.com/2014/08/04/blocking-domains-with-pfsense-using-dns-forwarder/

        1 Reply Last reply Reply Quote 0
        • JKnottJ
          JKnott
          last edited by

          You could create a dummy DNS entry for that host name.  Point it to some unused RFC 1918 address.  Then it won't go anywhere else.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 0
          • T
            tibbs
            last edited by

            @JKnott:

            You could create a dummy DNS entry for that host name.  Point it to some unused RFC 1918 address.  Then it won't go anywhere else.

            Where to create the entry?

            1 Reply Last reply Reply Quote 0
            • T
              tibbs
              last edited by

              Ok, got it this way:
              https://forum.pfsense.org/index.php?topic=132892.msg730573#msg730573

              1 Reply Last reply Reply Quote 0
              • JKnottJ
                JKnott
                last edited by

                @tibbs:

                Ok, got it this way:
                https://forum.pfsense.org/index.php?topic=132892.msg730573#msg730573

                That shows how to force DNS requests to the firewall.  Once there, you have to provide an address or the request will use the address provided from whatever DNS you use.  On the DNS Resolver and Forwarder pages, you can use host overrides to assign the dummy address to the host name.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                1 Reply Last reply Reply Quote 0
                • S
                  Soyokaze
                  last edited by

                  Proper "poor man's" way would be creating host override DNS entry in Resolver/Forwader and pointing to your local web server (with 'french-cooking.com' vhost). That way you:

                  • will impede dropper from obtaining it payload
                  • will know (from access logs on your web server) if you have infected machines on your network.

                  Real proper way would be implementing IDS/IPS system, but that is another story how to do.

                  Need full pfSense in a cloud? PM for details!

                  1 Reply Last reply Reply Quote 0
                  • F
                    Finger79
                    last edited by

                    https://ransomwaretracker.abuse.ch/ has DNS and IP blocklists that you can automatically import into the pfBlocker plug-in, which will create and update aliases, which can then be used in your firewall block rules for ingress and egress.

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      tibbs
                      last edited by

                      Thank you Guys.

                      https://ransomwaretracker.abuse.ch/ has DNS and IP blocklists that you can automatically import into the pfBlocker plug-in, which will create and update aliases, which can then be used in your firewall block rules for ingress and egress.

                      I know its off-topic, but can i safely install/use the latest pfBlocker plugin (2.1.1_8) for an older pfsense release (2.3.2-RELEASE)?

                      1 Reply Last reply Reply Quote 0
                      • K
                        kokkebaspe Banned
                        last edited by kokkebaspe

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • T
                          terryzb @Finger79
                          last edited by

                          @Finger79
                          I get a 503 error when hitting https://ransomwaretracker.abuse.ch/ from pfBlockerNG and the web. Temporarily down? Are there other ransomware tracking feeds for pfB? I didn't see any that specifically listed ransomware.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.