spyware alerts for <something>.fmb.la

[jbankstonfla]

this just started popping up for DNS queries inside going outbound, my PA440 is dropping the packets as a spyware threat. This is quite a new development, probably last 24 hours.

Example action below:

name-of-threatid eq 'generic:com.fresh.fmb.la'

anyone seen this before? I can't find anything on a Google nor a LiveCommunity search.

-Jeff

[JayGolf]

Hi @jbankstonfla ,

I'm unable to find info regarding this as well. I'll reach out internally to see if I can find answers for you. 

[NeilG]

Yes, I'm seeing this too. Appears to trigger when hitting via google dns on port 53,    but the site is actually https://fmb.la   Looks like curated Blocking list that Paloalto may be using from one of their Dynamic lists.  I'll post more info in a bit. 

[jbankstonfla]

hasn't happened in awhile, but just did, see attached pic. These were DNS queries from my internal DNS servers doing forwarders lookups for unknown resolutions to OpenDNS public servers. Running 11.1.3 code.

[jbankstonfla]

bam!  Just happened again as I posted the reply above, see next pic, this time to this community.

-Jeff

[jbankstonfla]

problem is back, 11.1.4 code and I noticed that anytime I set spyware inspection for outbound DNS servers, this alert comes up and the packets are dropped. There's just something out of kilter about how this inspection works because the source and destination servers are valid and working fine, I just had to stop using spyware inspection on outbound DNS traffic.

[laurence64]

Hi

Threat Vault has very little info actually on it but it was created in 2022 so seems to have been around for a while? https://threatvault.paloaltonetworks.com/?query=generic:com.fresh.fmb.la&type=dns-signatures you could put an exception into DNS security for this but I am not sure you would want to,  when doing IOC search while the DNS security result for the hostname you have is MALWARE and no PAN-DB categorization the Domain comes back as Benign, as @NeilG says the site itself is a blocklist, an nslookup from a Palo protected device gets sinkholed, so in this case I would suggest that this is the bad guys trying a bit of Domain Shadowing to try and get round less thorough security platforms.

Feels like the firewall is doing what it should.

Hope that helps!