Is i3cperxt.exe safe?
Unsigned executable disguised as a Word document with zero detections but extreme rarity.
The file presents as an Office Open XML document yet carries an .exe extension and is unsigned. No engine flagged it, but the combination of brand-new submission, missing signature, and filename mismatch warrants caution.
193ed51d140ba79d40…b91af52e34c69fRecommended 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.
The file presents as an Office Open XML document yet carries an .exe extension and is unsigned. No engine flagged it, but the combination of brand-new submission, missing signature, and filename mismatch warrants caution.
Zero detections across 74 engines is reassuring, yet the file is only hours old, has never been seen before, and is unsigned while masquerading as a document. The .exe extension on a docx file type is a classic delivery trick. Without signer history or prior benign samples, the risk cannot be dismissed.
What We Detected
74 engines scanned the sample; none returned a malicious, suspicious, or PUA label. The file metadata declares an Office Open XML Document, yet the submitted name ends in .exe and the payload is unsigned.
Threat Behavior
No sandbox execution data, dropped children, or contacted hosts are available. External intelligence sources (CIRCL, MalwareBazaar, YARAify) contain no matching rules or prior sightings.
What To Do Now
Do not open the file. If the document is expected from a trusted sender, request a re-submission with a correct .docx extension and digital signature. Otherwise treat it as potentially weaponised and delete or quarantine it.
Where this verdict could be wrong1 caveat
- Filename extension mismatch could be a packaging error rather than malice, but the combination of unsigned + rare_new + docx-vs-exe still outweighs that possibility.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero engine detections
- No malicious external-intel hits
- Filename claims executable while file type claims document
- Unsigned and brand new
- No prior benign history
Quarantine the file and request a properly signed, correctly named copy from the sender before any further handling.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 74engines flagged
- 1sources 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 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not runThis looks like a Windows executable, but no completed PE structure result is saved.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- i3cperxt.exe
- Format
- Office Open XML Document
- Code signing
- No verified publisher
- Size
- 5.9 MB
- Last analyzed
- Jul 24, 2026, 12:43 AM UTC
193ed51d140ba79d4036bf57bd49ab4f40ce83456089dce8c5b91af52e34c69fSafety & 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 i3cperxt.exe safe, or is it malware?
What is i3cperxt.exe?
How many antivirus engines detected i3cperxt.exe?
What should I do if I already ran i3cperxt.exe?
How do I remove i3cperxt.exe?
What is the SHA-256 hash of i3cperxt.exe?
How up to date is this analysis of i3cperxt.exe?
Community
Member reviews and reports for this exact file hash.