Is Office_2024_EN_64Bits.exe safe?
No antivirus engine detected malware, but the single runtime record's T1055 and LSASS-related indicators justify caution with this third-party Office installer.
All 75 antivirus engines avoided flagging this widely submitted, verified-signed executable, and the completed host check found no known harmful contacts. However, one sandbox record mapped activity to process injection and LSASS-related access, while the non-Microsoft signer has no established history, so the installer should be sourced directly from Microsoft instead.
04c3c5cf2f26c10a82…a1eb035327d605Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy 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 avoided flagging this widely submitted, verified-signed executable, and the completed host check found no known harmful contacts. However, one sandbox record mapped activity to process injection and LSASS-related access, while the non-Microsoft signer has no established history, so the installer should be sourced directly from Microsoft instead.
The strongest evidence is the complete absence of detections across 75 engines, including 17 tier-1 engines. One completed sandbox run did not produce a malicious verdict, and its observed Office download infrastructure had complete host-reputation coverage without a known harmful result. The sample is also widely submitted, is not statically packed, and has no corroboration from YARA rules or curated malware intelligence. Against that, the runtime record includes MITRE T1055 and LSASS-related activity, which are too sensitive to dismiss solely as installer noise. The signature verifies, but it belongs to Technik Markt TMA e.K. rather than Microsoft and has no historical sample record, leaving uncertainty about this unofficial Office wrapper.
What We Detected
No detections were reported by 75 antivirus engines, including all 17 tier-1 engines. The executable has a valid signature from Technik Markt TMA e.K., has appeared in 4,876 submissions from 3,289 sources, and produced no YARA or curated malware-intelligence matches. The signer is not on the curated publisher list and has no established sample history.
Threat Behavior
One completed sandbox run did not issue a malicious verdict. It showed Office setup activity and downloads from Microsoft-associated infrastructure, and the host-reputation check covered all 15 observed domains and 15 observed IPs without identifying a known harmful or suspicious host. However, the runtime evidence maps activity to MITRE T1055 and includes an LSASS-related indicator; these can be associated with credential theft or injection, although the saved evidence does not prove either action occurred. Ten dropped children were inspected with no malicious child identified, but each remains individually unclassified.
What To Do Now
Avoid using an unofficial Office installer when Microsoft provides an official installation channel. Obtain Office through Microsoft or an authorized organization portal, verify the expected publisher before execution, and keep endpoint protection enabled. If this file has already run, perform a full security scan and review recent account activity if unexpected prompts or behavior occurred.
Where this verdict could be wrong4 caveats
- The runtime record maps activity to T1055 and includes LSASS-related process activity, both of which merit caution even though the sandbox did not issue a malicious verdict.
- The certificate is valid, but signing.trustedPublisher.matched=false and signerStats.found=false, so there is no established publisher history.
- All 10 inspected dropped children lack individual verdicts; hasMaliciousChild=false therefore does not establish that each child is benign.
- Community annotations are mixed, and adversarialInputFlags.commentInjectionSuspected=true means their text was downweighted rather than treated as authoritative.
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.
- All 17 tier-1 engines reported no detection.
- The single sandbox verdict was non-malicious.
- Complete reputation coverage found no known harmful or suspicious observed hosts.
- The file is verified-signed, common, older, and not likely packed.
- Runtime evidence includes MITRE T1055.
- A heuristic associates observed process activity with LSASS.
- The signer is not Microsoft and signing.trustedPublisher.matched=false.
- signerStats.found=false, leaving no established publisher history.
- All 10 dropped children remain individually unclassified.
Prefer Microsoft's official Office download or deployment channel rather than this third-party wrapper. Keep endpoint protection enabled and run a full scan if the executable has already been launched.
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
Partial20 of 40 contacted hosts were cross-checked; coverage is incomplete.
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
- 27MITRE ATT&CK techniques
- 15spawned processes
- 47network 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: 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).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
Office_2024_EN_64Bits.exe
04c3c5cf2f26c10a82444d4f9498557c89a4521331dace6427a1eb035327d605
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c ""C:\Users\<USER>\AppData\Local\Temp\start.bat" "
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
start.bat
C:\Users\<USER>\AppData\Local\Temp\start.bat
04Isolated runtime analysis - Written fileObserved
Click To Run.bat
C:\Users\<USER>\AppData\Local\Temp\package\Click To Run.bat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
f.c2r.ts.cdn.office.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
07Contacted-host cross-check - +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.
- f.c2r.ts.cdn.office.net
- www.microsoft.com
- officeclient.microsoft.com
- ecs.office.com
- mrodevicemgr.officeapps.live.com
- mobile.events.data.microsoft.com
- res.public.onecdn.static.microsoft
- ecs-office.s-0005.dual-s-msedge.net
- s-0005.dual-s-msedge.net
- fg.microsoft.map.fastly.net
- 199.232.214.172
- a83f:8110:1800:0:200:0:0:0
- 192.168.0.20
- 151.101.22.172
- 23.55.140.42
- 52.109.8.89
- 52.123.128.14
- 52.109.0.136
- 20.42.73.31
- 23.196.193.245
- http://f.c2r.ts.cdn.office.net/pr/7983bac0-e531-40cf-be00-fd24fe66619c/Office/Data/v64_16.0.17932.20638.cab
- http://f.c2r.ts.cdn.office.net/pr/7983bac0-e531-40cf-be00-fd24fe66619c/Office/Data/v64_16.0.17932.20286.cab
- http://f.c2r.ts.cdn.office.net/pr/7983bac0-e531-40cf-be00-fd24fe66619c/Office/Data/16.0.17932.20286/i640.cab
- http://f.c2r.ts.cdn.office.net/pr/7983bac0-e531-40cf-be00-fd24fe66619c/Office/Data/16.0.17932.20286/s641033.cab
- http://f.c2r.ts.cdn.office.net/pr/7983bac0-e531-40cf-be00-fd24fe66619c/Office/Data/16.0.17932.20286/s640.cab
- http://f.c2r.ts.cdn.office.net/pr/7983bac0-e531-40cf-be00-fd24fe66619c/Office/Data/16.0.17932.20286/stream.x64.x-none.dat
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\DmsClient\C2RReleaseData\C2RReleaseDataRequestCache
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\DmsClient\C2RReleaseData\C2RReleaseDataResponseCache
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\DmsClient\C2RReleaseData\C2RReleaseDataCacheTimestamp
- \REGISTRY\A\{508300F3-4C43-2137-4E3F-ABA2DD734B23}\Root\InventoryDevicePnp\acpi/genuineintel_-_intel64_family_6_model_79_-____________intel(r)_xeon(r)_cpu_@_2.20ghz/_0\DriverVerVersion
- \REGISTRY\A\{508300F3-4C43-2137-4E3F-ABA2DD734B23}\Root\InventoryDevicePnp\acpi/genuineintel_-_intel64_family_6_model_79_-____________intel(r)_xeon(r)_cpu_@_2.20ghz/_1\DriverVerVersion
- \REGISTRY\A\{508300F3-4C43-2137-4E3F-ABA2DD734B23}\Root\InventoryDevicePnp\acpi/pnp0303/4&2c352a27&0\DriverVerVersion
- C:\Users\<USER>\AppData\Local\Temp\start.bat
- C:\Users\<USER>\AppData\Local\Temp\package\Click To Run.bat
- C:\Users\<USER>\AppData\Local\Temp\package\configuration.xml
- C:\Users\<USER>\AppData\Local\Temp\package\setup.exe
- C:\Users\<USER>\AppData\Local\Microsoft\Office\16.0\WebServiceCache\AllUsers\officeclient.microsoft.com\F6D85B46-4ECA-48BD-BB1E-9CC774436773
- C:\Users\<USER>\AppData\Local\Microsoft\Office\OTele\setup.exe.db-journal
- C:\Users\<USER>\AppData\Local\Temp\v64_16.0.17932.20638CheckReachableB44BD78D-6572-4C35-95DA-A9885F301CDC
- C:\Users\<USER>\AppData\Local\Temp\OfficeC2R099137F8-AB46-4896-B701-DC74392306E8OfficeC2R10F7CAF9-AC70-4761-98C9-3954C1A04E87\v64.hash
- C:\Users\<USER>\AppData\Local\Temp\OfficeC2R099137F8-AB46-4896-B701-DC74392306E8OfficeC2R10F7CAF9-AC70-4761-98C9-3954C1A04E87\VersionDescriptor.xml
- C:\Users\<USER>\AppData\Local\Temp\OfficeC2R099137F8-AB46-4896-B701-DC74392306E8OfficeC2R10F7CAF9-AC70-4761-98C9-3954C1A04E87
- Local\2BF388D5-6F8C-40A0-A7EE-996D005C4E14_Office16
- Local\OfficeSetupBootstrapper
- \Sessions\1\BaseNamedObjects\Global\SyncRootManager
- \Sessions\1\BaseNamedObjects\Local\OfficeSetupBootstrapper
- \Sessions\1\BaseNamedObjects\Office.16.916BB0BF-2D21-4499-83C7-555DB4C3F8E8
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 14469967c269e753b8b1…5a8fd7Never scannednever seen before
- 79d4c1981a9fb6dc0ea8…8cb548Never scannednever seen before
- f21b6351e00b4745a432…9afd37Never scannednever seen before
- 4d2a271248b921295681…0fe511Never scannednever seen before
- 6584cfdbbc24bf0c1ba3…cce12dNever scannednever seen before
- 08f271887ce94707da82…7473f1Never scannednever seen before
- 08c71258148843c5f342…399de6Never scannednever seen before
- 1d5b3b2ec11826763cd2…7aa81eNever scannednever seen before
- c88a8b2a37f07b406d54…f68db2Never scannednever seen before
- 2163cdf0700b8428bd08…25df78Never 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 / 75engines flagged
- 3,289sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,289 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: Office_2024_EN_64Bits.exe — 04c3c5cf2f26c10a82444d4f9498557c89a4521331dace6427a1eb035327d605
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c ""C:\Users\<USER>\AppData\Local\Temp\start.bat" "
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: start.bat — C:\Users\<USER>\AppData\Local\Temp\start.bat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Click To Run.bat — C:\Users\<USER>\AppData\Local\Temp\package\Click To Run.bat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: f.c2r.ts.cdn.office.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved 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\System32\svchost.exe -k NetworkService -pSandbox 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.exe
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Office_2024_EN_64Bits.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Technik Markt TMA e.K.
- Size
- 3.4 MB
- Last analyzed
- Sep 26, 2026, 3:06 AM UTC
04c3c5cf2f26c10a82444d4f9498557c89a4521331dace6427a1eb035327d605Safety & 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 run 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 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 Office_2024_EN_64Bits.exe safe, or is it malware?
What is Office_2024_EN_64Bits.exe?
How many antivirus engines detected Office_2024_EN_64Bits.exe?
I already downloaded and ran Office_2024_EN_64Bits.exe — what should I do?
How do I remove Office_2024_EN_64Bits.exe?
Is Office_2024_EN_64Bits.exe digitally signed?
What is the SHA-256 hash of Office_2024_EN_64Bits.exe?
How up to date is this analysis of Office_2024_EN_64Bits.exe?
Community
Member reviews and reports for this exact file hash.