Is ROLLBACK.EXE safe?
The Microsoft-signed executable drew no detections from 75 engines, while its generic YARA and direct-IP signals lack corroborating malicious behavior.
The executable has a verified Microsoft Windows signature, and none of 75 antivirus engines detected it, including all 17 reporting tier-1 engines. Two generic YARA matches and direct-IP activity merit context, but no malicious sandbox verdict, dropped payload, persistence, or named malware family supports them.
d3be11867b58def4bd…97b770f664b74cRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
The executable has a verified Microsoft Windows signature, and none of 75 antivirus engines detected it, including all 17 reporting tier-1 engines. Two generic YARA matches and direct-IP activity merit context, but no malicious sandbox verdict, dropped payload, persistence, or named malware family supports them.
The executable carries a verified Microsoft Windows signature that matches a curated trusted publisher. None of 75 antivirus engines flagged it, and all 17 reporting tier-1 engines were silent. One completed sandbox run produced no malicious verdict, although it recorded T1134 and several direct-IP contacts. No complete host-reputation result is available because the contacted-host cross-check was not saved. The two YARA matches concern certificate presence and broad concealment or entropy characteristics, with the latter rule explicitly acknowledging false positives. These generic findings are outweighed by the signature, broad engine agreement, lack of malicious runtime corroboration, and a prior safe same-signer sample.
What We Detected
ROLLBACK.EXE is a 64-bit Windows executable with a verified Microsoft Windows signature and a trusted-publisher match for Microsoft. None of 75 antivirus engines reported a detection, including all 17 reporting tier-1 engines. A previous same-signer sample also received a safe assessment.
Threat Behavior
One completed sandbox run recorded mostly common system activity and one offensive-class technique, T1134. It also observed several direct-IP contacts, but no complete host-reputation cross-check is available, so those no complete contacted-host reputation result was available or malicious from this evidence. The run produced no malicious sandbox verdict, persistence indicators, written files, or dropped hashes. Two community YARA rules matched: one detects a digital certificate, while the other broadly covers overlay, obfuscation, encryption, spoofing, hiding, or entropy traits and explicitly notes possible false positives.
What To Do Now
Confirm that the file came through Microsoft or a trusted Windows update or recovery channel and verify that its digital signature remains valid before running it. Keep endpoint protection enabled; investigate further if the file appeared unexpectedly or outside a normal Windows maintenance context.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.DirectIpC2 fired after external IP contacts were observed, while contactedHosts=null means no complete reputation assessment is available for those hosts.
- externalIntel.yaraify.ruleCount=2 is normally concerning, although neither matching rule identifies a malware family and one explicitly warns of false positives.
- T1134 was observed during runtime analysis; this technique can be abused for access-token manipulation, but no malicious sandbox verdict, persistence indicator, or dropped file accompanied it.
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 antivirus engines reported a detection.
- All 17 reporting tier-1 engines returned no detection.
- The Microsoft Windows signature is verified and signing.trustedPublisher.matched=true.
- One sandbox run produced no malicious verdict, persistence indicator, or dropped payload.
- PE analysis reports highEntropyCode=false and likelyPacked=false.
- T1134 was observed in one sandbox run.
- Direct-IP network activity was recorded without a complete contacted-host reputation check.
- YARAify matched Sus_Obf_Enc_Spoof_Hide_PE, a broad rule that may indicate concealment traits but explicitly permits false positives.
- signing.signerStats.totalSamples=1 provides only limited historical signer-statistics depth.
Use the file only if it came from a trusted Microsoft or Windows maintenance source and its signature still validates. Keep endpoint protection enabled and quarantine it for review if its origin is unexpected.
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
Partial10 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 9MITRE ATT&CK techniques
- 6spawned processes
- 10network contacts
- 9filesystem & 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
ROLLBACK.EXE
d3be11867b58def4bd6015477e24342021fc40fd90e71f7e1597b770f664b74c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\ROLLBACK.EXE
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\wuapihost.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
199.232.210.172
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
40.126.28.13
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- 199.232.210.172
- 40.126.28.13
- 20.12.23.50
- 204.79.197.203
- 20.99.133.109
- 192.229.211.108
- 192.168.0.36
- 23.213.37.172
- 192.168.0.161
- 23.55.140.42
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FB8.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2083.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER20B3.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER22A7.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER22A8.tmp.csv
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 0 / 75engines flagged
- 73sources 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
The hash appears in a known-software reference database.
Verdict inputView chapterProvenanceObservedSourceReference software databaseObserved at - 03
The file has a valid code signature from Microsoft Windows.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: ROLLBACK.EXE — d3be11867b58def4bd6015477e24342021fc40fd90e71f7e1597b770f664b74c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\ROLLBACK.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\wuapihost.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 199.232.210.172 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 40.126.28.13 — 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.
- PE_Digital_Certificate
- Sus_Obf_Enc_Spoof_Hide_PE
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.
Evidence199.232.210.172 · 40.126.28.13 · 20.12.23.50
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
- ROLLBACK.EXE
- Format
- Win32 EXE
- Code signing
- Signature valid: Microsoft Windows
- Size
- 157.4 KB
- Last analyzed
- Sep 14, 2026, 4:08 AM UTC
d3be11867b58def4bd6015477e24342021fc40fd90e71f7e1597b770f664b74cSafety & 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
Run it only when it came from the developer's official site or another source you independently trust.
- 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 ROLLBACK.EXE safe?
What is ROLLBACK.EXE?
How many antivirus engines detected ROLLBACK.EXE?
Is ROLLBACK.EXE digitally signed?
What is the SHA-256 hash of ROLLBACK.EXE?
Is it safe to run ROLLBACK.EXE?
How up to date is this analysis of ROLLBACK.EXE?
Community
Member reviews and reports for this exact file hash.