An antivirus detection is a warning, not a final verdict. This workflow helps you decide whether a quarantined file is genuinely malicious or a false positive before restoring it, using provenance, hashes, digital signatures, reputation checks, controlled testing, and vendor review.
Overview
Antivirus products can occasionally flag legitimate software, scripts, installers, development tools, or newly compiled files. This is more likely when a file is uncommon, heavily packed, unsigned, downloaded from an unusual location, or behaves in a way that resembles malware. A false positive is possible, but it should never be assumed simply because the file is useful or familiar.
The safest approach is to leave the file in quarantine while you collect evidence. Do not restore it first and investigate later. A practical assessment should answer five questions:
- Where did the file come from, and was the source trustworthy?
- Does its cryptographic hash match a known-good copy?
- Is the file digitally signed, and can the signature be verified?
- Do independent reputation checks support or contradict the detection?
- Can the vendor explain or reclassify the alert?
No single signal proves that a file is safe. A valid signature can be stolen or misused, a clean reputation result can become outdated, and a new threat may not yet be recognized by other scanners. Treat the result as a confidence assessment rather than a binary guarantee.
Step-by-step workflow
1. Record the detection before changing anything
Open the antivirus history, protection log, or quarantine view and record the detection name, file path, detection time, product version, and action taken. If the product displays a severity, behavior category, or threat identifier, include that as well. Save a screenshot or export the event when practical.
Do not delete the quarantine record. It provides useful context if you later contact the software publisher or submit the file to the antivirus vendor. If the alert appeared after a software update, build, or installer launch, record that relationship too.
2. Confirm the file’s provenance
Ask how the file reached the device. A download from the official publisher’s site, a managed software repository, or a controlled internal build process is stronger evidence than an attachment, cracked-software site, unexpected redirect, or file-sharing link. Check the original download page, package name, version, and release notes if they are available.
When possible, download a fresh copy directly from the publisher using a separate browser session or trusted device. Do not use the quarantined copy as the only reference. Compare the new file’s name, size, version information, and hash with the quarantined item if you can do so without restoring it.
3. Calculate and compare the file hash
A hash is a fingerprint calculated from the file’s contents. The most useful comparison is between the quarantined file and a hash published by the legitimate developer through an official channel. If the values match, the files are substantially the same for practical verification purposes. If they differ, stop and investigate rather than treating the files as interchangeable.
On Windows, an administrator or user can calculate a SHA-256 hash with PowerShell:
Get-FileHash "C:\Path\to\file.exe" -Algorithm SHA256
On macOS or Linux, a common command is:
shasum -a 256 /path/to/file
Use the exact algorithm shown by the publisher. MD5 or SHA-1 values may still appear in older documentation, but they are weaker choices for establishing file integrity. Never paste sensitive source code, private documents, credentials, or proprietary binaries into a public reputation service merely to obtain a hash result.
4. Inspect the digital signature
A digital signature can help confirm who signed a Windows executable and whether it changed after signing. In File Explorer, open the file’s properties and look for a Digital Signatures tab, then inspect the signer and signature status. On macOS, code-signing information can be inspected with system tools such as codesign; the exact result depends on the type of application or package.
Check the signer against the expected publisher, not just whether a signature exists. An unsigned file is not automatically malicious, particularly for internal scripts or developer builds, but it deserves additional scrutiny. A signature warning, an unexpected signer, or a signature that does not validate should be treated as a reason not to restore the file.
5. Use multi-engine reputation checks carefully
You can submit a hash, or in some cases a file, to a reputable multi-engine scanning service. Start with the hash to avoid uploading the file unnecessarily. Compare the detection count, names, file type, age, and behavioral labels rather than focusing on a single vendor result.
These services have limitations. A low detection count does not prove safety, and a high count can include duplicate or overly broad classifications. Public submissions may also expose the file or its metadata to other parties. Do not upload confidential business files, unreleased software, credentials, customer data, or proprietary code unless your organization has approved that process.
6. Test only in an isolated environment
If the file still needs to be examined, use a disposable virtual machine or isolated test device with no access to production systems, personal files, shared drives, or sensitive credentials. Keep network access disabled unless the test specifically requires it, and treat any request for administrator privileges, persistence, security-tool changes, or unusual outbound connections as significant evidence.
Do not open a suspicious document on your normal workstation, and do not rely on a virtual machine as a perfect safety boundary. If the file is associated with ransomware, credential theft, remote access, or a suspected targeted attack, preserve the evidence and involve a qualified incident-response or security team instead of experimenting locally.
7. Ask the vendor to review the detection
Antivirus vendors commonly provide a false-positive submission form or a process within their security product. Use the current submission route listed in the product’s support documentation. Include the file hash, detection name, product version, operating system, source URL or publisher, and a concise explanation of why you believe the file is legitimate.
If the file belongs to a third-party application, contact that publisher too. Ask for a verified download location and the expected SHA-256 hash. Keep the file quarantined until the antivirus vendor or publisher provides a credible explanation. A vendor reclassification is stronger evidence than an informal claim that “the antivirus is wrong.”
8. Restore only when the evidence supports it
Restore the file only after checking its provenance, hash, signature, reputation, and vendor status. If it is restored, launch it in the smallest possible context and monitor the antivirus, operating system, and network logs. Avoid creating a broad exclusion for an entire folder or file type.
If an exclusion is unavoidable, make it as narrow and temporary as possible: specify the exact file or controlled path, document the reason and approver, set a review date, and remove the exception when the software is updated or the task is complete.
Tools and handoffs
The verification process works best when each tool has a limited role:
- Antivirus history and quarantine: preserve the alert, detection name, and original path.
- Hash utilities: compare the file with an official, independently obtained value.
- Signature inspection: check publisher identity and file integrity.
- Reputation services: provide additional signals, subject to privacy and coverage limits.
- Isolated test systems: observe behavior without exposing production assets.
- Vendor and publisher support: resolve classification disputes and obtain authoritative hashes.
For developer teams, add hash and signature checks to release documentation and artifact pipelines. For small organizations, record the decision in a ticket or incident log. The small business endpoint security policy template can help turn one-off decisions into a repeatable process. Container and software supply-chain files need the same discipline; see how to scan Docker images and dependencies for a related workflow.
Quality checks
Before allowing a quarantined file, confirm that the evidence is consistent. The source should be credible, the hash should match an official value or a known-good internal artifact, and the signature should identify the expected publisher when signing is appropriate. The detection should be understood, not merely ignored. A second scanner can add context, but it should not replace provenance or controlled analysis.
Look for warning signs that justify leaving the file blocked: an unknown or changing source, a mismatched hash, a revoked or unexpected signer, suspicious persistence behavior, requests to disable protection, credential prompts unrelated to the task, or unexplained network activity. If any of these appear, preserve the file and logs rather than repeatedly restoring it.
After a confirmed false positive, update the application and antivirus definitions, then retest. Remove temporary exclusions and verify that protection remains active. If the device may already have executed the file, follow a post-cleanup checklist rather than assuming quarantine resolved every risk; the post-malware-removal security checklist covers that next stage.
When to revisit
Revisit this workflow whenever a security product changes its detection, a trusted application receives an update, a build tool produces a new artifact, or a previously excluded file changes. A past false positive does not permanently make future versions safe. Recalculate the hash and review the signature for every materially different release.
Review documented exclusions at a defined interval and whenever the responsible person, software publisher, endpoint platform, or antivirus product changes. Also refresh your notes after major operating-system or security-tool updates because quarantine controls, log locations, submission forms, and command behavior can change.
When an alert appears, use this short action list:
- Leave the file quarantined.
- Record the alert and obtain the original source.
- Calculate and compare a SHA-256 hash.
- Check the signer and reputation without exposing sensitive data.
- Submit the evidence to the antivirus vendor or software publisher.
- Restore only with documented justification, then remove any temporary exclusion.
This approach reduces the chance of both outcomes that matter: executing a real threat and permanently weakening protection because a legitimate tool was flagged once.