Is Greenshot-INSTALLER-1.3.315-RELEASE.exe safe?
No antivirus engine detected the signed Greenshot installer, but offensive runtime mappings and multiple structural YARA matches warrant source verification before execution.
All 75 antivirus engines were silent, including 17 tier-1 products, and the executable carries a verified Thomas Braun signature. However, one sandbox mapped credential dumping, process injection, and defense-evasion techniques, while seven YARA rules matched structural features; verify the download against Greenshot’s official release before running it.
9bb4971e729a2ad161…c7d0f80f8c0fd3Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
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 were silent, including 17 tier-1 products, and the executable carries a verified Thomas Braun signature. However, one sandbox mapped credential dumping, process injection, and defense-evasion techniques, while seven YARA rules matched structural features; verify the download against Greenshot’s official release before running it.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including all 17 tier-1 products. The executable is signed with a verified certificate for Thomas Braun, and no conflicting brand identity was found, but there is no historical signer record available. One completed sandbox run produced no malicious verdict, although it mapped T1003, T1055, T1562.001, and other offensive techniques. Seven YARA rules also matched, but the disclosed names concern compiler, certificate, and TLS-section characteristics rather than a specific malware family. Host-reputation coverage was incomplete, and the similar-file results are weak because every match shares only an imphash across different publishers. Overall, the evidence favors a legitimate installer with anomalous automated behavior mappings, but independent source verification remains appropriate.
What We Detected
None of 75 antivirus engines flagged the executable, and all 17 tier-1 engines reported no detection. The file has a verified signature from Thomas Braun, its installer-style filename matches its observed installation flow, and no brand conflict was detected. Seven community YARA rules matched, including HUNTING_SUSP_TLS_SECTION and pe_detect_tls_callbacks, but the available rule names do not identify a malware family.
Threat Behavior
One sandbox run mapped potentially offensive activity to T1003, T1055, T1562.001, and related techniques. It did not produce a malicious sandbox verdict, identify persistence indicators, or yield a known-malicious dropped child among the 10 inspected files; however, those child verdicts remain unknown. The host cross-check inspected only one contact and therefore does not provide complete reputation coverage for all observed IPs and the Greenshot update URL.
What To Do Now
Confirm SHA-256 9bb4971e729a2ad1612e8aa2fa490b69c33af7f42515f9b642c7d0f80f8c0fd3 against the hash published through Greenshot's official release channel, and confirm that Windows shows the Thomas Braun signature as valid. Keep endpoint protection enabled and avoid running the file if it came from an advertisement, mirror, unsolicited message, or other unverified source.
Where this verdict could be wrong4 caveats
- The runtime mappings T1003, T1055, and T1562.001 can indicate credential access, process injection, and defense evasion, though the single sandbox supplied no malicious verdict.
- YARAify returned 7 matches, but the disclosed rules primarily identify Borland artifacts, Certum certificates, and TLS-section features rather than a named malware family.
- contactedHosts.inspected=1 does not cover all 15 contacted IPs plus the observed URL, so no complete host-reputation conclusion is available.
- signing.signerStats.found=false means the verified 'Thomas Braun' signature lacks established historical backing in this dataset.
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 detected malware or suspicious content.
- All 17 tier-1 engines reported no detection.
- The 'Thomas Braun' code signature is verified.
- brandMismatch was not detected.
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false.
- One sandbox mapped nine offensive techniques, including T1003, T1055, and T1562.001.
- externalIntel.yaraify.ruleCount=7, including a suspicious TLS-section hunting rule.
- signing.signerStats.found=false provides no historical signer reputation.
- Host-reputation inspection did not cover every observed IP and URL.
- All 10 inspected dropped children have unknown individual verdicts.
Use the file only after matching its hash and verified Thomas Braun signature with Greenshot’s official release channel. Keep antivirus and 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 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete8 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
- 10spawned processes
- 21network contacts
- 33filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Accessed operating-system credential data, which can expose saved passwords.
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Searched files or settings where passwords and keys may be stored.
High concern: Attempted to impair or bypass security controls.
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
Greenshot-INSTALLER-1.3.315-RELEASE.exe
9bb4971e729a2ad1612e8aa2fa490b69c33af7f42515f9b642c7d0f80f8c0fd3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Greenshot-INSTALLER-1.3.315-RELEASE.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-DCPMS.tmp\Greenshot-INSTALLER-1.3.315-RELEASE.tmp" /SL5="$50178,3032110,791552,C:\Users\<USER>\Desktop\Greenshot-INSTALLER-1.3.315-RELEASE.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Greenshot-INSTALLER-1.3.315-RELEASE.tmp
C:\Users\<USER>\AppData\Local\Temp\is-DCPMS.tmp\Greenshot-INSTALLER-1.3.315-RELEASE.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-RHNNF.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
13.107.226.70
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.21.10.247
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.
- 13.107.226.70
- 104.21.10.247
- 150.171.73.13
- 23.216.147.194
- 104.18.34.93
- 104.92.251.90
- 192.0.77.2
- 104.16.80.73
- 173.194.203.132
- 172.253.117.94
- https://getgreenshot.org/update-feed.json
- C:\Users\<USER>\AppData\Local\Temp\is-DCPMS.tmp\Greenshot-INSTALLER-1.3.315-RELEASE.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-RHNNF.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-RHNNF.tmp\isxdl.dll
- C:\Users\<USER>\AppData\Local\Programs\Greenshot\Dapplo.Windows.Clipboard.dll
- C:\Users\<USER>\AppData\Local\Programs\Greenshot\HtmlAgilityPack.dll
- C:\Users\<USER>\AppData\Local\Programs\Greenshot\Plugins
- C:\Users\<USER>\AppData\Local\Programs\Greenshot
- C:\Users\<USER>\AppData\Local\Programs\Greenshot\is-U008N.tmp
- C:\Users\<USER>\AppData\Local\Programs\Greenshot\is-H85L9.tmp
- C:\Users\<USER>\AppData\Local\Programs\Greenshot\is-9JE3C.tmp
- cversions.3.m
- C__Users_Bruno_AppData_Local_Greenshot_Greenshot.log_rolling
- Local\F48E86D3-E34C-4DB7-8F8F-9A0EA55F0D08
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 1d3ef8698281e7cf7371…ba1183Never scannednever seen before
- be1068d1af240549afcd…029834Never scannednever seen before
- ac3706ebbb78cfba74e5…0aba8fNever scannednever seen before
- f53d719cf57e098fa366…086d59Never scannednever seen before
- a059e2749d4ee647c185…c3084bNever scannednever seen before
- b624949df8b0e3a6153f…6610f3Never scannednever seen before
- 14638b5b3a694ad5ded1…828afcNever scannednever seen before
- bd42daf25165e3deaa7b…458060Never scannednever seen before
- 550a7c35debe1d1b038e…574589Never scannednever seen before
- f0ec81e0646237f92089…c2806fNever 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.
- 8rule hits recorded
- 0 / 75engines flagged
- 2,776sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Thomas Braun.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Greenshot-INSTALLER-1.3.315-RELEASE.exe — 9bb4971e729a2ad1612e8aa2fa490b69c33af7f42515f9b642c7d0f80f8c0fd3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Greenshot-INSTALLER-1.3.315-RELEASE.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-DCPMS.tmp\Greenshot-INSTALLER-1.3.315-RELEASE.tmp" /SL5="$50178,3032110,791552,C:\Users\<USER>\Desktop\Greenshot-INSTALLER-1.3.315-RELEASE.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Greenshot-INSTALLER-1.3.315-RELEASE.tmp — C:\Users\<USER>\AppData\Local\Temp\is-DCPMS.tmp\Greenshot-INSTALLER-1.3.315-RELEASE.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-RHNNF.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.226.70 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.21.10.247 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- Borland
- certum_issuer
- detect_certum_issuer
- HUNTING_SUSP_TLS_SECTION
- pe_detect_tls_callbacks
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.EXEMITRE T1003 (OS Credential Dumping) mapped by at least one sandbox run.
The 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.
Evidence13.107.226.70 · 104.21.10.247 · 150.171.73.13
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Greenshot-INSTALLER-1.3.315-RELEASE.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Thomas Braun
- Size
- 3.8 MB
- Last analyzed
- Sep 11, 2026, 3:25 PM UTC
9bb4971e729a2ad1612e8aa2fa490b69c33af7f42515f9b642c7d0f80f8c0fd3Safety & 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 install 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. Download a fresh installer from the developer's official site or an official app store.
- 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 Greenshot-INSTALLER-1.3.315-RELEASE.exe safe, or is it malware?
What is Greenshot-INSTALLER-1.3.315-RELEASE.exe?
How many antivirus engines detected Greenshot-INSTALLER-1.3.315-RELEASE.exe?
What should I do if I already installed Greenshot-INSTALLER-1.3.315-RELEASE.exe?
How do I remove Greenshot-INSTALLER-1.3.315-RELEASE.exe?
Is Greenshot-INSTALLER-1.3.315-RELEASE.exe digitally signed?
What is the SHA-256 hash of Greenshot-INSTALLER-1.3.315-RELEASE.exe?
How up to date is this analysis of Greenshot-INSTALLER-1.3.315-RELEASE.exe?
Community
Member reviews and reports for this exact file hash.