Is colab-SailPoint-IIQ-on-Docker-main.zip safe?
No antivirus engine detected this ZIP archive, although its very recent appearance and lack of runtime analysis warrant normal caution before extracting it.
All 75 antivirus engines returned without a malicious or suspicious detection, including 17 tier-1 engines. No external intelligence source corroborated a threat, but the archive is newly observed and was not executed in a sandbox, so its contents should still be extracted cautiously.
c5c5bde5494befb926…574feed68a7cfeRecommended 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 17 tier-1 engines. No external intelligence source corroborated a threat, but the archive is newly observed and was not executed in a sandbox, so its contents should still be extracted cautiously.
Static scanning produced 0 detections across 75 antivirus engines, with all 17 reporting tier-1 engines finding nothing malicious. MalwareBazaar, CIRCL, and YARAify supplied no corroborating threat intelligence. The archive has only one recorded submission and was first observed very recently, which limits reputation-based assurance. No completed sandbox run is available, so the behavior of scripts or binaries inside the ZIP was not observed. Similar-file history trends benign, but those records match only the broad ZIP file type and therefore provide weak support.
What We Detected
The ZIP archive received 0 malicious and 0 suspicious detections from 75 antivirus engines. All 17 reporting tier-1 engines, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast, returned without a detection. MalwareBazaar, CIRCL, and YARAify also supplied no matching threat intelligence.
Threat Behavior
No completed sandbox observation is available, so the archive's runtime behavior and the behavior of any enclosed scripts or executables remain untested. No complete contacted-host reputation result is available either. The file is newly observed with only one recorded source and submission, so it has little established reputation.
What To Do Now
Obtain the archive from the expected project or repository and inspect its extracted contents before running scripts, containers, or executables. Keep endpoint protection enabled, and use an isolated environment if the source or contents cannot be independently verified.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new and file.ageDays=0 provide almost no established reputation.
- behaviour=null means no runtime execution was observed, and contactedHosts=null means no complete host-reputation result is available.
- The 4/5 prior safe outcomes in similarHashes are only file-type matches, not content, signer, or imphash matches.
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 a malicious or suspicious result
- tier1Malicious=0 and tier1ReportedClean=17
- externalIntel.malwareBazaar.hit=false
- externalIntel.yaraify.ruleCount=0
- brandMismatch.detected is not present
- file.ageDays=0 — first observed very recently
- prevalence.uniqueSources=1 and prevalence.timesSubmitted=1
- behaviour=null — no completed runtime observation
- contactedHosts=null — no complete host-reputation result
- ZIP archives may contain components not meaningfully assessed through archive-level reputation alone
Verify that the ZIP came from the expected project source, then inspect its extracted files before execution. Keep endpoint protection enabled and use isolation for any untrusted scripts or containers.
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
Complete3 of 3 independent reference sources completed.
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
- 1sources 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
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- colab-SailPoint-IIQ-on-Docker-main.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 1.0 MB
- Last analyzed
- Oct 1, 2026, 5:52 PM UTC
c5c5bde5494befb92699cb706b9a4948937467cd1fc8c520ca574feed68a7cfeSafety & 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 colab-SailPoint-IIQ-on-Docker-main.zip safe?
What is colab-SailPoint-IIQ-on-Docker-main.zip?
How many antivirus engines detected colab-SailPoint-IIQ-on-Docker-main.zip?
What is the SHA-256 hash of colab-SailPoint-IIQ-on-Docker-main.zip?
Is it safe to open or extract colab-SailPoint-IIQ-on-Docker-main.zip?
How up to date is this analysis of colab-SailPoint-IIQ-on-Docker-main.zip?
Community
Member reviews and reports for this exact file hash.