File scan report
Verdict Safe
Is Capys-
Only 1 of the 68 antivirus engines that checked it flagged this archive, while higher-confidence engines and the combined sandbox result supplied no supporting malware evidence.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website you got it from.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
1 of 68 flagged
- Flagged 1
- No detection 67
- No result 7
- Code signing Not applicable
- Test run Completed
- First seen 2d ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Bkav was the only engine to flag the archive, using a generic label; none of the higher-confidence engines agreed. The combined sandbox verdict was clean, and no malicious child, named injection target, malware-specific rule, or hostile host corroborated the detection, making a false positive highly likely.
Only 1 of the 68 antivirus engines that checked it flagged the archive, and that detection came from Bkav with a generic label. None of the higher-confidence engines reported a detection. The combined sandbox verdict was clean, and the runs recorded no named injection target or other high-risk technique with supporting artefacts. No malware-specific community rule, public sample-database listing, malicious child, or hostile contacted host supported Bkav's result. Confidence is moderated because the archive was first seen on Nov 2, 2026 and its contents were not examined by our static analysis.
What We Detected
Only 1 of the 68 antivirus engines that checked it flagged the archive. Bkav assigned a generic malware label, while none of the higher-confidence engines agreed, which strongly suggests an isolated false positive.
Threat Behavior
The combined sandbox verdict was clean. Although the sandbox summary mapped process injection, file encryption, and defence tampering techniques, it recorded none of the concrete artefacts needed to substantiate those actions, including any named injection target. No malicious child, malware-specific community rule, public sample-database listing, or hostile contacted host provided corroboration.
What To Do Now
The available evidence supports ordinary use if the archive came from the source you expected. Because our static analysis did not inspect the archive contents and it was first seen on Nov 2, 2026, keep security software enabled and rescan after extracting before running any executable.
Where this verdict could be wrong2 caveats
- Bkav labels the archive W32.Malware.7919C28B, although no other engine corroborates that generic label.
- The archive was first seen on Nov 2, 2026 and our static analysis did not inspect its contents, so the available evidence cannot exclude every concealed component.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the higher-confidence antivirus engines flagged the archive.
- The combined sandbox verdict was clean and recorded no named injection target.
- No malicious child or hostile contacted host was identified.
- Malware-specific community rules and the checked public sample database produced no match.
- Bkav assigned a generic malware label, although no other engine corroborated it.
- The archive was first seen on Nov 2, 2026 and has a limited submission history.
- Our static analysis did not inspect the archive contents.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 2 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 2isolated sandbox runs
- 15sandbox rule tags
- 9spawned processes
- 0network contacts
- 39filesystem & mutex artifacts
Includes the sandbox verdicts, 15 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 68 antivirus engines that checked it flags it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
The saved verdict treats these detections as likely false positives.
- BkavW32.Malware.7919C28B
File fingerprint
- Last analyzed
- Nov 2, 2026, 5:46 AM UTC
- SHA-256
103373a8e69398ea0014f6ef3a3439db962454b6bac7107627ee2c06fc4bac2c- SHA-1
47cdb93ad4352308a593fd1a998f659ea8e0bb3c- MD5
ceaee9bd12b2002a7987a229eef21605
About this file
Capys-AA-Macro-v3.7.zip is a ZIP file of 76.6 MB.
- Type and size
- ZIP · 76.6 MB
- Signer
- Not applicable
- First seen
- Nov 2, 2026On VirusTotal.
- Submitted by
- 10 distinct sources
First scanned
Includes every engine result (75), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Capys-AA-Macro-v3.7.zip safe?
What is Capys-AA-Macro-v3.7.zip?
How many antivirus engines detected Capys-AA-Macro-v3.7.zip?
What is the SHA-256 hash of Capys-AA-Macro-v3.7.zip?
Is it safe to open or extract Capys-AA-Macro-v3.7.zip?
How up to date is this analysis of Capys-AA-Macro-v3.7.zip?
Community
Member reviews and reports for this exact file hash.
