Reply to thread

Message

<blockquote data-quote="Morro" data-source="post: 945093" data-attributes="member: 1765">I like how fast F-Secure solved this. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite116" alt=":D" title="Big grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />[SPOILER]Greetings,Thank you for your submission.Our analysis has found that the file you submitted is clean.We have identified the issue as a False Positive, which will be resolved automatically via F-Secure&#039;s Security Cloud.&nbsp;&nbsp;For environments where applications change or get often updated, Deepguard may keep on detecting a new version of the application as &#039;rare&#039; or &#039;suspicious&#039;.&nbsp;For these cases we&#039;d appreciate if you could submit additional samples that are still detected in response to this email (inside a password-protected zip). This is so that the offending detection that caused the false positive can be fixed.&nbsp;&nbsp;Alternatively, you may want to configure a temporary Exclusion inside your F-Secure product while the issue is investigated:[/SPOILER]So Upnorth mentioning code can change was right on target alright. Why do I sound surprised about, considering what he does here. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> (Sorry Upnorth if it sounds like that.)And now PrivaZer works again, I also made an exclusion for PrivaZer as F-Secure mentioned. (Just to be safe for future updates.)</blockquote>

[QUOTE="Morro, post: 945093, member: 1765"] I like how fast F-Secure solved this. :D [SPOILER] Greetings, Thank you for your submission. Our analysis has found that the file you submitted is clean. We have identified the issue as a [U]False Positive[/U], which will be resolved automatically via F-Secure's Security Cloud. For environments where applications change or get often updated, Deepguard may keep on detecting a new version of the application as [U]'rare' or 'suspicious'[/U]. For these cases we'd appreciate if you could submit [U]additional samples that are still detected[/U] in response to this email (inside a password-protected zip). This is so that the offending detection that caused the false positive can be fixed. Alternatively, you may want to configure a temporary [B]Exclusion[/B] inside your F-Secure product while the issue is investigated: [/SPOILER] So Upnorth mentioning code can change was right on target alright. Why do I sound surprised about, considering what he does here. :) (Sorry Upnorth if it sounds like that.) And now PrivaZer works again, I also made an exclusion for PrivaZer as F-Secure mentioned. (Just to be safe for future updates.) [/QUOTE]

Verification