Is Adobe Installer safe?
A verified Adobe signature and minimal antivirus detection are reassuring, but process-injection, LSASS-access, and destructive-technique mappings warrant caution pending source verification.
Only 1 of 75 engines detected the file, and no high-trust engine corroborated the generic Trojan label. The verified Adobe signature and lack of malicious children are reassuring, but the recorded T1055 activity and apparent LSASS targeting are unusually risky for an installer, so obtain a fresh copy through Adobe's official channel.
431400157f37bcf467…62f885a811276cRecommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Only 1 of 75 engines detected the file, and no high-trust engine corroborated the generic Trojan label. The verified Adobe signature and lack of malicious children are reassuring, but the recorded T1055 activity and apparent LSASS targeting are unusually risky for an installer, so obtain a fresh copy through Adobe's official channel.
The executable carries a verified Adobe Inc. signature with a trusted-publisher match and no detected brand conflict. Only Yandex flagged it among 75 engines, while all reporting high-trust engines were non-detecting and no family consensus formed. One completed sandbox run nevertheless mapped activity to T1055, T1485, T1486, and T1562.001, with a heuristic also indicating LSASS targeting. No malicious sandbox verdict, malicious dropped child, YARA rule, or known-malware database match corroborated those mappings. Host-reputation coverage was incomplete because only one of the observed network hosts was inspected, so the no complete contacted-host reputation result was available. Overall, the signature and broad engine silence favor a false positive, but the unusual runtime indicators justify verification before execution.
What We Detected
Yandex was the only detector among 75 engines, using the generic label Trojan.GenAsa!rBStHMRk3Wo. No high-trust engine flagged the executable, and no tier-1 family consensus formed. The file is signed with a verified Adobe Inc. certificate, matches the claimed Adobe brand, and has one signer-matched prior sample carrying a favorable decision.
Threat Behavior
One completed sandbox run recorded mappings for process injection (T1055), data destruction (T1485), data encryption for impact (T1486), and impairment of defenses (T1562.001). A separate heuristic reported activity targeting LSASS, which is a serious concern, although the sandbox itself issued no malicious verdict. Ten dropped children were inspected without a malicious child finding, and neither YARAify nor MalwareBazaar supplied corroboration. Network reputation coverage was incomplete: contactedHosts.inspected=1 did not cover all five contacted IPs and the observed URL.
What To Do Now
Do not rely solely on the filename or signature. Download a fresh installer directly through Adobe Creative Cloud or Adobe's official website, compare its SHA-256 hash and signature, and keep endpoint protection enabled. Avoid running this particular copy if its origin cannot be confirmed.
Where this verdict could be wrong4 caveats
- The runtime evidence includes T1055 and apparent LSASS targeting, which are difficult to dismiss as ordinary installer activity even though behaviour.hasMaliciousSandboxVerdict=false.
- peAnalysis.likelyPacked=true with UPX1 entropy 7.91 and file.reputation=-11 adds uncertainty around an otherwise verified Adobe signature.
- Yandex produced the sole detection, 'Trojan.GenAsa!rBStHMRk3Wo', but no other engine or external-intelligence source corroborated that generic label.
- contactedHosts.inspected=1 provides only partial reputation coverage for the five contacted IPs and one URL.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Verified signature from Adobe Inc. with signing.trustedPublisher.matched=true.
- Only 1/75 engines detected the file, with engines.tier1Malicious=0.
- No tier-1 family consensus and no malicious sandbox verdict.
- No malicious child among 10 inspected dropped files.
- MalwareBazaar and YARAify returned no hits.
- Runtime mapping includes process injection technique T1055.
- MalwareTips.Synth.CredentialDumper reports apparent access targeting lsass.exe.
- Runtime mappings include T1485, T1486, and T1562.001.
- peAnalysis.likelyPacked=true and UPX1 entropy is 7.91.
- file.reputation=-11.
- Host-reputation inspection covered only one observed host.
Replace this copy with one downloaded directly through Adobe Creative Cloud or Adobe's official website, then verify the Adobe Inc. signature before running it. Keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 6 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete4 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
- 31MITRE ATT&CK techniques
- 15spawned processes
- 6network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
Adobe Installer
431400157f37bcf46734bbb21be3cc03e9fe206395f131d08162f885a811276c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\After_Effects_Set-Up_747d.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\Connect
04Isolated runtime analysis - Written fileObserved
WAM.log
C:\Users\<USER>\AppData\Local\Temp\CreativeCloud\ACC\WAM.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.28.11
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
8.8.8.8
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 150.171.28.11
- 8.8.8.8
- 52.6.228.48
- 34.233.49.149
- 162.159.36.2
- https://cc-api-data.adobe.io
- \Device\ConDrv\Connect
- C:\Users\<USER>\AppData\Local\Temp\CreativeCloud\ACC\WAM.log
- C:\Users\<USER>\AppData\Local\Temp\Adobe\com.adobe.dunamis\dunamis-2026-07-20_20-36-47.log
- C:\Users\<USER>\AppData\Roaming\com.adobe.dunamis\f65a88c9-12b3-4201-a633-87cf11b91fa8\v1\0
- C:\Users\<USER>\AppData\Roaming\com.adobe.dunamis\f65a88c9-12b3-4201-a633-87cf11b91fa8\v1\0\meta_events\manifest
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Adobe\webview2\After_Effects_Set-Up_747d.exe\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Local\Adobe\webview2\After_Effects_Set-Up_747d.exe\EBWebView\afa14f47-c1d3-4c38-8d6c-da033d84476b.tmp
- C:\Users\<USER>\AppData\Local\Adobe\webview2\After_Effects_Set-Up_747d.exe\EBWebView\Default\Code Cache\js\index-dir\the-real-index
- WAM.log
- Local\ChromeProcessSingletonStartup!
- __OMADM_NAMED_MUTEX__
- Global\OneSettingQueryMutex+compat+encapsulation
- Global\{3EBE6875-9C4E-4782-8A43-275AFFFCA6FB}
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- 94a3fa01c16f2edb2e21…f75b77Never scannednever seen before
- 840a9873aee1c0d78f63…968dc7Never scannednever seen before
- bc84c7767196a1609ef0…1509baNever scannednever seen before
- 65dc0882fbf6c4a7c827…91160fNever scannednever seen before
- c736834631bf84d8d0c9…19a0bcNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never 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.
- 4rule hits recorded
- 1 / 75engines flagged
- 161sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including Yandex.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Adobe Inc..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Adobe Installer — 431400157f37bcf46734bbb21be3cc03e9fe206395f131d08162f885a811276c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\After_Effects_Set-Up_747d.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WAM.log — C:\Users\<USER>\AppData\Local\Temp\CreativeCloud\ACC\WAM.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.28.11 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 8.8.8.8 — 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.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.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.
Evidence150.171.28.11 · 52.6.228.48 · 34.233.49.149Packed PE with sandbox-observed network activity AND engine flags. Signed packed software exists legitimately, but a signed + packed + flagged binary is a signed dropper pattern.
Evidencehttps://cc-api-data.adobe.io
1 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Adobe Installer
- Format
- Win32 EXE
- Code signing
- Signature valid: Adobe Inc.
- Size
- 3.4 MB
- Last analyzed
- Sep 17, 2026, 3:20 PM UTC
431400157f37bcf46734bbb21be3cc03e9fe206395f131d08162f885a811276cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Adobe Installer safe, or is it malware?
What is Adobe Installer?
How many antivirus engines detected Adobe Installer?
What should I do if I already opened Adobe Installer?
How do I remove Adobe Installer?
Is Adobe Installer digitally signed?
What is the SHA-256 hash of Adobe Installer?
How up to date is this analysis of Adobe Installer?
Community
Member reviews and reports for this exact file hash.