Is PigPack.zip safe?
No antivirus engine detected PigPack.zip, and its circulation across 565 sources provides additional reassurance, although no runtime analysis was completed.
All 75 antivirus engines returned without a malicious or suspicious detection, including 16 reporting tier-1 engines. The archive has also circulated through 565 sources, but no sandbox execution or complete contacted-host reputation check is available, so ordinary caution remains appropriate when extracting its contents.
e54137ae98cb34c732…ff76f7dd4aef5aRecommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines returned without a malicious or suspicious detection, including 16 reporting tier-1 engines. The archive has also circulated through 565 sources, but no sandbox execution or complete contacted-host reputation check is available, so ordinary caution remains appropriate when extracting its contents.
The archive received zero malicious and zero suspicious detections among 75 antivirus engines. Sixteen tier-1 engines reported no detection, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast. Its 622 submissions from 565 sources provide useful prevalence support, and the available CIRCL check supplied no known-malicious indication. No heuristic, similar-hash, user-feedback, brand-mismatch, or dropped-child concern was recorded. However, behaviour is null and contactedHosts is null, meaning neither runtime activity nor complete network reputation was assessed.
What We Detected
PigPack.zip received no malicious or suspicious detections from 75 antivirus engines. Sixteen reporting tier-1 engines found no detection, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast. The archive has been submitted 622 times by 565 sources, which reduces concern that it is an obscure, newly encountered sample.
Threat Behavior
No completed sandbox observation is available because behaviour is null. The evidence therefore does not establish how extracted files behave when opened. contactedHosts is also null, so no complete host-reputation result is available; YARAify coverage was skipped as well.
What To Do Now
Keep endpoint protection enabled and scan extracted files before opening them. Obtain the archive from its expected source, and avoid running unexpected executables or scripts contained inside.
Where this verdict could be wrong2 caveats
- The ZIP archive was not executed in a sandbox because behaviour=null, so scanner results do not establish what extracted contents might do at runtime.
- contactedHosts=null and YARAify was skipped, leaving gaps in host-reputation and researcher-rule coverage.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines reported malicious or suspicious results
- tier1Malicious=0 and tier1ReportedClean=16
- 565 unique sources and 622 submissions
- triggeredHeuristics is empty
- brandMismatch is null and recentFeedback is empty
- behaviour=null: no completed runtime observation
- contactedHosts=null: no complete contacted-host reputation cross-check
- externalIntel.yaraify was skipped
- ZIP containers can hold files that require separate inspection after extraction
Keep endpoint protection enabled, verify the archive's source, and scan its extracted contents before opening them. Avoid executing unexpected scripts or programs inside the ZIP.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 565sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- PigPack.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 4.1 MB
- Last analyzed
- Sep 11, 2026, 2:44 PM UTC
e54137ae98cb34c7322ffbb22c17f6c933d228cfec1a8694a9ff76f7dd4aef5aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or extract it only when its sender or download source has been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is PigPack.zip safe?
What is PigPack.zip?
How many antivirus engines detected PigPack.zip?
What is the SHA-256 hash of PigPack.zip?
Is it safe to open or extract PigPack.zip?
How up to date is this analysis of PigPack.zip?
Community
Member reviews and reports for this exact file hash.