Is Aav_ColorLab_1_0_rc2_x64.msi safe?
No antivirus engine detected this long-observed installer, while uncorroborated process-injection and direct-IP indicators warrant obtaining it only from a trusted source.
All 76 antivirus engines were free of detections, including 17 tier-1 engines, and the installer has been observed since 2011. One sandbox mapped activity to T1055 and T1485 and recorded a direct-IP contact, but produced no malicious runtime verdict; the unsigned package should still be sourced and verified carefully.
6208766af9251cac17…8e5b91dddd939fRecommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed 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 76 antivirus engines were free of detections, including 17 tier-1 engines, and the installer has been observed since 2011. One sandbox mapped activity to T1055 and T1485 and recorded a direct-IP contact, but produced no malicious runtime verdict; the unsigned package should still be sourced and verified carefully.
The strongest evidence is the absence of detections across 76 antivirus engines, including no alerts from 17 tier-1 engines. The file has also been observed for more than 15 years across 69 sources and 80 submissions, making an undiscovered widespread threat less likely. One completed sandbox run recorded T1055 and T1485 mappings, but it did not issue a malicious verdict, and no inspected child was identified as malware. Research feeds supplied no family, signature, or YARA corroboration. Confidence is reduced because the MSI is unsigned, every dropped child remains unclassified, and no complete saved host-reputation check exists for the contacted IP.
What We Detected
No detections were reported among 76 antivirus engines, and all 17 reporting tier-1 engines were free of alerts. The MSI has been observed since 2011, with 69 sources and 80 submissions, and no matching malware family was supplied by the available research feeds.
Threat Behavior
One completed sandbox run mapped activity to T1055 and T1485 and recorded contact with 142.251.183.94. These mappings can be concerning, but the sandbox did not issue a malicious verdict, no persistence indicator was recorded, and none of the 10 inspected children was identified as malicious. However, those children remain unclassified, and no complete saved host-reputation result is available for the contacted IP.
What To Do Now
Use the installer only if it came from the developer or another trusted distribution channel. Because the package is unsigned, verify its SHA-256 value, keep endpoint protection enabled, and avoid installation if its origin cannot be established.
Where this verdict could be wrong4 caveats
- The installer is unsigned: signing.applicable=true and signing.signed=false, so publisher identity cannot be authenticated.
- MalwareTips.Synth.ProcessInjection fired from a T1055 mapping, and T1485 was also recorded; neither technique was corroborated by an explicit malicious sandbox verdict.
- MalwareTips.Synth.DirectIpC2 fired for 142.251.183.94, but contactedHosts=null means the address did not receive a complete saved reputation cross-check.
- All 10 inspected dropped children have unknown verdicts, so droppedChildren.hasMaliciousChild=false is not equivalent to confirmed-clean child files.
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/76 antivirus engines detected the file
- 17 tier-1 engines reported no detection
- No malicious sandbox verdict
- No inspected child identified as malicious
- Observed since 2011 across 69 sources and 80 submissions
- Unsigned Windows Installer despite signing being applicable
- Sandbox mapped possible process injection to T1055
- Sandbox recorded T1485
- Direct-IP contact to 142.251.183.94 lacks a complete saved host-reputation check
- All 10 dropped children remain unclassified
Obtain the MSI only from a trusted publisher channel and verify SHA-256 6208766af9251cac1764a0e62ed3a8d19878251f287aea1fea8e5b91dddd939f before use. Keep endpoint protection enabled during installation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 12MITRE ATT&CK techniques
- 4spawned processes
- 1network contacts
- 39filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Aav_ColorLab_1_0_rc2_x64.msi
6208766af9251cac1764a0e62ed3a8d19878251f287aea1fea8e5b91dddd939f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\Explorer.EXE
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\install.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ngen.log
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
04Isolated runtime analysis - Written fileObserved
~DFB74D91E55AB1AA7C.TMP
C:\Windows\Temp\~DFB74D91E55AB1AA7C.TMP
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
142.251.183.94
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 142.251.183.94
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Windows\Temp\~DFB74D91E55AB1AA7C.TMP
- C:\Windows\Temp\~DF7451BB60C3382136.TMP
- C:\Windows\Temp\~DF1E09CDB7F5142B6E.TMP
- C:\Windows\Temp\~DFBBF33C60FF47B6C0.TMP
- C:\Config.Msi\CMP48F6.tmp
- C:\Config.Msi
- C:\Windows\Installer\24474.msi
- C:\Windows\WinSxS\InstallTemp\20241009232914426.0
- C:\Windows\WinSxS\InstallTemp\20241009232914426.0\amd64_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_a17e7c1e.cat
- Global\_MSIExecute
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
- \Sessions\1\BaseNamedObjects\Global\MSILOG_f121c5081d8dd5aGOL.4fb51ISM_pmeT_lacoL_ataDppA_egroeg_sresU_:C
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 3cd011617319709b2d20…1bc476Never scannednever seen before
- 3e5aefa515dd45c78d75…548b51Never scannednever seen before
- 49e22b24d757e08e0933…86e257Never scannednever seen before
- e5f2cf93deb7c430ae6d…1f0fe5Never scannednever seen before
- 0f47291635c5b2a6879c…305edeNever scannednever seen before
- 6f9fbb683aaf3529b134…6bef73Never scannednever seen before
- cb4a75549139007bf6ce…e070beNever scannednever seen before
- ebe17688c7dcea0bf887…234dabNever scannednever seen before
- 9ebb560f3efa2a55c926…518ff8Never scannednever seen before
- f20398cee3fef2afc996…a7854bNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 76engines flagged
- 69sources 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 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 80 times from 69 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Aav_ColorLab_1_0_rc2_x64.msi — 6208766af9251cac1764a0e62ed3a8d19878251f287aea1fea8e5b91dddd939f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\install.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ngen.log — C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ~DFB74D91E55AB1AA7C.TMP — C:\Windows\Temp\~DFB74D91E55AB1AA7C.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 142.251.183.94 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXEThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence142.251.183.94
0 of 76 engines flagged this file
View all 76 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
- Aav_ColorLab_1_0_rc2_x64.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 2.2 MB
- Last analyzed
- Sep 8, 2026, 2:57 PM UTC
6208766af9251cac1764a0e62ed3a8d19878251f287aea1fea8e5b91dddd939fSafety & 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
Install it only when it came from the developer's official site or an official app store.
- 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 Aav_ColorLab_1_0_rc2_x64.msi safe?
What is Aav_ColorLab_1_0_rc2_x64.msi?
How many antivirus engines detected Aav_ColorLab_1_0_rc2_x64.msi?
What is the SHA-256 hash of Aav_ColorLab_1_0_rc2_x64.msi?
Is it safe to install Aav_ColorLab_1_0_rc2_x64.msi?
How up to date is this analysis of Aav_ColorLab_1_0_rc2_x64.msi?
Community
Member reviews and reports for this exact file hash.