Is Phising Email.msg safe?
Suspicious file assessment
1 high-confidence signature or behavior rule matched this file.
c24e3287ccf64fcf5a…1d846640258d76Recommended 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. Ask the sender to confirm the message through a separate trusted channel or resend it.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
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
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 5 contacted hosts were cross-checked; coverage is incomplete.
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
- 17MITRE ATT&CK techniques
- 10spawned processes
- 5network contacts
- 40filesystem & 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: Searched files or settings where passwords and keys may be stored.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
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
Phising Email.msg
c24e3287ccf64fcf5a9c7ab6db474f792ececee1d24b3885701d846640258d76
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\Explorer.EXE
02Isolated runtime analysis - ProcessObserved
Observed process
wmiadap.exe /F /T /R
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
WmiApRpl_new.h
C:\Windows\System32\wbem\Performance\WmiApRpl_new.h
04Isolated runtime analysis - Written fileObserved
WmiApRpl.h
C:\Windows\System32\wbem\Performance\WmiApRpl.h
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
52.110.6.8
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
216.145.217.37
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.
- 52.110.6.8
- 216.145.217.37
- 108.156.224.87
- https://image-processing-service.au-1.mimecastcybergraph.com/v2/banners?e=v4piKlh60PAPoPESQGiUygIFY7M-IdzdwgLb0-gAvZpTPxTAo3a5ciaHeK1PYNY6go0vuBEnFH0mQeA5Q24EuX233PSM62537GFTogEjOpEqyHFfNmzJ3b_rkb4Qtsx0W30HlkJfDnu-SPXdfnZNmGqlfiE41TjNdsoaPcMgKu7hN_SXcGF04hq6QVf8g-GAJOO6GGm7gIb11TYU-YnWjbU-scWwrgYUy7BDWqDSMVHOlVUyYfAnxvYjMiTJHBG1_AFzA7mE9hol9ujIfv_C0TU8CV1fnTORdfwV2KLqDtp3Lu5CZbcLWGe65dyu3A50z6blnBk57qHCudFLnAnFJIQ-B9iJGnOJdniWCTqprb8oBYOtFLKitpsi_nKpRAlPxEZFyCVsggKIBsHHwEwUWZX6MxXvKZzEi0GCkqKMFC7JMFLcGxgGtCyti3E=
- https://banner.au-1.mimecastcybergraph.com/BXxLT4HtNrigBPppauYU8A_1780881818-144605a979850af985ffb56b5adaf1b1a75d73b85bb6db156f52deae.png
- C:\Windows\System32\wbem\Performance\WmiApRpl_new.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl_new.ini
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- C:\Windows\System32\perfc009.dat
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl_new.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- C:\Windows\System32\wbem\Performance\WmiApRpl_new.ini
- C:\Windows\INF\WmiApRpl\0009\WmiApRpl.ini
- Global\ADAP_WMI_ENTRY
- Global\RefreshRA_Mutex
- Global\RefreshRA_Mutex_Lib
- Global\RefreshRA_Mutex_Flag
- Installing
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 458d7b862c71abbdfffd…5093edNever scannednever seen before
- a48c02fd36302685b5fb…ffa0a8Never scannednever seen before
- 055fb0442e2f3e787ae4…921c88Never scannednever seen before
- 97da3c982874ec87dcba…014346Never scannednever seen before
- 71e7f7b8deb46f98c972…d00f28Never scannednever seen before
- 89b2a9ad7d42f90b4a97…503e07Never scannednever seen before
- 6539622808a7d841b85d…c774ecNever scannednever seen before
- 260d54ebc92d8a772234…a9829cNever scannednever seen before
- 104ef282a2f46d748560…8cd56aNever scannednever seen before
- eb16c763abed997b0987…212c0eNever 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.
- 3rule 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 4 times from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Phising Email.msg — c24e3287ccf64fcf5a9c7ab6db474f792ececee1d24b3885701d846640258d76
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — wmiadap.exe /F /T /R
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: WmiApRpl_new.h — C:\Windows\System32\wbem\Performance\WmiApRpl_new.h
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WmiApRpl.h — C:\Windows\System32\wbem\Performance\WmiApRpl.h
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.110.6.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 216.145.217.37 — 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.
Evidence52.110.6.8 · 216.145.217.37 · 108.156.224.87
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Phising Email.msg
- Format
- Outlook
- Code signing
- Not applicable to this file type
- Size
- 1.2 MB
- Last analyzed
- Jul 24, 2026, 7:41 AM UTC
c24e3287ccf64fcf5a9c7ab6db474f792ececee1d24b3885701d846640258d76Safety & 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 message and use a fresh copy from a trusted source. Ask the sender to confirm the message through a separate trusted channel or resend it.
- 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 Phising Email.msg safe, or is it malware?
What is Phising Email.msg?
How many antivirus engines detected Phising Email.msg?
I already downloaded and opened Phising Email.msg — what should I do?
How do I remove Phising Email.msg?
What is the SHA-256 hash of Phising Email.msg?
How up to date is this analysis of Phising Email.msg?
Community
Member reviews and reports for this exact file hash.