Is M Centers.exe safe?
Unsigned packed executable showing process-injection and network stager behaviour with zero AV detections.
The file is unsigned and packed, exhibits four offensive MITRE techniques including process injection, and triggered dropper/stager heuristics. No antivirus engine flagged it, yet community YARA rules link it to Raccoon Stealer V2.
5f405489a7f6c67bbc…f05580fb58a2d3Recommended 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 is unsigned and packed, exhibits four offensive MITRE techniques including process injection, and triggered dropper/stager heuristics. No antivirus engine flagged it, yet community YARA rules link it to Raccoon Stealer V2.
Seventy-five engines returned zero malicious detections, yet the sample is unsigned, packed, and demonstrated process injection plus direct-IP network activity in sandbox. The combination of high-severity heuristics and a Raccoon Stealer YARA match outweighs the clean engine results, placing the file in mixed-signals territory.
What We Detected
Unsigned 64-bit PE, high-entropy sections, likely packed. Sandbox recorded T1055 process injection, service creation (T1543.003), defence evasion (T1562.001), and reflective loading (T1620). Sixteen external IPs were contacted without domain names.
Threat Behavior
Network activity and dropped files match classic stager/dropper patterns. Community YARA rules flag the binary as Raccoon Stealer V2 and several exploit PoCs, although no engine currently corroborates these labels.
What To Do Now
Do not execute. Keep endpoint protection enabled. Submit the sample to a multi-engine sandbox for deeper behavioural logging before any further trust decision.
Where this verdict could be wrong1 caveat
- Zero engine detections despite 71 engines reporting; widespread prevalence over 777 days suggests possible false-positive heuristics.
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 detections across 75 engines
- Widely submitted over 777 days
- Unsigned executable
- High-entropy packed code
- Process-injection techniques observed
- Direct-IP network traffic
- YARA match for Raccoon Stealer
Treat as suspicious; block pending additional sandbox or dynamic analysis.
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 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 25MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
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: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
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
M Centers.exe
5f405489a7f6c67bbcc130ebbb272a99bde94b0d01b1b958f6f05580fb58a2d3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 6704 -s 460
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
2c8ff4f3-0abc-4a58-9320-8913a102f3b8
C:\ProgramData\Microsoft\Windows\WER\Temp\2c8ff4f3-0abc-4a58-9320-8913a102f3b8
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.216.147.61
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.185.48
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.
- 23.216.147.61
- 20.99.185.48
- 23.198.171.50
- 20.99.186.246
- 192.168.0.45
- 23.216.147.55
- 104.71.214.69
- 184.25.191.235
- 192.168.0.17
- 184.29.167.249
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\2c8ff4f3-0abc-4a58-9320-8913a102f3b8
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\054cadca-62f4-4894-89e7-b5efd8f70dc6
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC75.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF231.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF3B8.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC75.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF231.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess6704
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\58423796-c930-4d02-96c4-3cfb77692580
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7384
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 612b144068c5d065f38b…9c602cNever scannednever seen before
- 304c3b9b70568f5058a3…70f361Never scannednever seen before
- bef31bd0c15c2d2ea308…8c968fNever scannednever seen before
- 88876e60315fe341c5dc…6048edNever scannednever seen before
- b77e8237fe4d42dfa35c…626b12Never scannednever seen before
- 8e19692f07709863b0a9…d6af5dNever 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 / 75engines flagged
- 3,656sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 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 hash has a long, established submission history across 3,656 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: M Centers.exe — 5f405489a7f6c67bbcc130ebbb272a99bde94b0d01b1b958f6f05580fb58a2d3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 6704 -s 460
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 2c8ff4f3-0abc-4a58-9320-8913a102f3b8 — C:\ProgramData\Microsoft\Windows\WER\Temp\2c8ff4f3-0abc-4a58-9320-8913a102f3b8
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.216.147.61 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.185.48 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: infostealer
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.
Evidence"C:\Users\<USER>\Desktop\program.exe"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.
Evidence23.216.147.61 · 20.99.185.48 · 23.198.171.50Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence23.216.147.61
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
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
- M Centers.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.6 MB
- Last analyzed
- Aug 14, 2026, 3:59 PM UTC
5f405489a7f6c67bbcc130ebbb272a99bde94b0d01b1b958f6f05580fb58a2d3Safety & 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 M Centers.exe safe, or is it malware?
What is M Centers.exe?
How many antivirus engines detected M Centers.exe?
I already downloaded and ran M Centers.exe — what should I do?
How do I remove M Centers.exe?
What kind of malware is M Centers.exe?
What is the SHA-256 hash of M Centers.exe?
How up to date is this analysis of M Centers.exe?
Community
Member reviews and reports for this exact file hash.