06-11-2021 09:42 AM
We are investigating alerts of this DNS signature for x1.c.lencr.org.
I'd expect that a match for a clear text string in a DNS Request that it is very unlikely this is a false detection.
However to get alerts so quickly after this signature creation, suggests we are either very unlucky or a very common public internet resource if causing this fly-by access. Anyone else receiving this threat alert shortly after an apparent WF update.
06-15-2021 01:08 PM
This is a false positive. Palo Alto support provided the following:
I understand you are looking for a reason why this URL was marked as malware and why it flipped back. This domain is not malware, it was accidentally released last night, and as soon as we realized it was flip to shareware and disabled it. We are in the process of taking steps, such as adding this and some subdomains under lencr.org found in our database in a restrictive white list, domains under that list can't be released to malware. That step will avoid the similar FP case is caused in future.
06-15-2021 02:09 PM
Thanks for letting me know.
06-15-2021 04:20 PM
This signature is been disabled, and this domain( including some of the sub-domain) are categorized as Computer and Internet Info, Low Risk.
let me know if you have any more question
06-25-2021 08:04 AM
We are still seeing this domain show up as a confidence of 4 for botnet. Is anyone seeing the same? (or should I post this as a new discussion?)
Repeatedly visited (12) the same malicious URL x1.c.lencr.org/
06-25-2021 08:49 AM - edited 06-25-2021 08:51 AM
Showing up as a PA threat for the DNS query or for the URL on a block list? The original thread was for a DNS lookup threat of supposed malware. In our logs we were getting DNS threat hits and blocks from approximately 6/11 16:30 GMT until 6/15 7:45 GMT. We have not had any threat alerts since, though we continue to see intermittent traffic to the destination.
The x1.c.lencr.org DNS/URL is not a threat itself (that I have been able to find). It is a valid Lets Encrypt domain and returns a certificate revocation list when queried. In our case we tracked it down to a component of Sophos making the queries (doing HTTP GET for the root doc with a modifier: if changed since Sep 4 2020, it hasn't been so a 304 Not Modified was returned). It appears that suspected malware may have also been querying the URL (probably for a Lets Encrypt cert generated for the malware) and the entire domain was erroneously included as a threat.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!