This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
About goku123
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About goku123
03-15-2022
551Posts
61Likes
213Solutions
Mar 15, 2022Last Visited
User
Activity
User
Profile
Latest posts by goku123
| Subject | Views | Posted |
|---|---|---|
| 2479 | 10-14-2021 11:17 AM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 10-14-2021 11:17 AM | |
| 1 Like | 08-04-2016 08:55 AM | |
| 1 Like | 08-08-2013 01:33 PM | |
| 1 Like | 04-03-2013 05:50 AM | |
| 1 Like | 06-13-2013 05:43 AM |
User Badges
Community Statistics
| Member Since | 07-18-2011 11:50 AM |
| Date Last Visited | 03-15-2022 07:26 PM |
| Posts | 551 |
| Total Likes Received | 59 |
10-14-2021
11:17 AM
1 Kudo
Hi @ShaneMcG
When you query for an AV signature name or Signature ID in Threatvault, the sha256 hashes reported in Threatvault are the sha256 hashes of files for which this signature was generated.
e.g. If you search for the following:
Name: Virus/Win32.WGeneric.brwesg Sig id: 438164772
Threatvault shows 318f37ae7d23f954c51f3aef2d06edaaec60e01639131f2efb801cbab7168fec as one of the sample SHA256 hashes for this signature. This sample 318f3.. was deemed to be malware in the WildFire sandbox and thus the signature shows the association as coverage for this sample.
However, if the file transfer that triggered a signature was not for one of the hashes listed or no other malware was found, as @OtakarKlier suggested, please report this via a case and a support expert can help with next steps.
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks