Is MBSetup.exe safe?
Safe file assessment
0 of 76 antivirus engines flagged the file.
0b9465643cd2609856…0b59430c97bf41Recommended 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.
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 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete8 signature or behavior rules matched.
External intel
Partial1 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 32MITRE ATT&CK techniques
- 10spawned processes
- 2network contacts
- 17filesystem & 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
MBSetup.exe
0b9465643cd2609856e7ebdebc34296670a2b388c2bcf6e5ee0b59430c97bf41
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\MbamSetup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
mbsetup.log
C:\Users\<USER>\AppData\Local\Temp\mbsetup.log
04Isolated runtime analysis - Written fileObserved
mbamtestfile.dat
C:\ProgramData\mbamtestfile.dat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
16.145.101.152
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
api2.amplitude.com
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.
- 16.145.101.152
- https://api2.amplitude.com/batch
- C:\Users\<USER>\AppData\Local\Temp\mbsetup.log
- C:\ProgramData\mbamtestfile.dat
- C:\Program Files (x86)\mbamtestfile.dat
- C:\Windows\System32\drivers\mbamtestfile.dat
- C:\Windows\System32\wbem\repository\WRITABLE.TST
- C__Users_Bruno_Desktop_MbamSetup.exe
- Global\OneSettingQueryMutex+compat+encapsulation
- C__Users_azure_Downloads_MbamSetup.exe
- \Sessions\1\BaseNamedObjects\C__Users_user_Desktop_MbamSetup.exe
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- ede1645ea6d74ba2267a…6cea2aNever scannednever seen before
- 3c3b166e33d1fdf710f0…51d9d8Never 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.
- 8rule hits recorded
- 0 / 76engines flagged
- 2,946sources 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 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The file has a valid code signature from Malwarebytes Inc.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: MBSetup.exe — 0b9465643cd2609856e7ebdebc34296670a2b388c2bcf6e5ee0b59430c97bf41
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\MbamSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: mbsetup.log — C:\Users\<USER>\AppData\Local\Temp\mbsetup.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: mbamtestfile.dat — C:\ProgramData\mbamtestfile.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 16.145.101.152 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: api2.amplitude.com — 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.
- APT_Sandworm_ArguePatch_Apr_2022_1
- Check_VBox_Description
- DebuggerCheck__API
- DetectEncryptedVariants
- FreddyBearDropper
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
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.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.
Evidence16.145.101.152
0 of 76 engines flagged this file
View all 76 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- MBSetup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Malwarebytes Inc
- Size
- 2.7 MB
- Last analyzed
- Apr 24, 2026, 5:17 AM UTC
0b9465643cd2609856e7ebdebc34296670a2b388c2bcf6e5ee0b59430c97bf41Safety & 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 MBSetup.exe safe?
What is MBSetup.exe?
How many antivirus engines detected MBSetup.exe?
Is MBSetup.exe digitally signed?
What is the SHA-256 hash of MBSetup.exe?
Is it safe to run MBSetup.exe?
How up to date is this analysis of MBSetup.exe?
Community
Member reviews and reports for this exact file hash.
