Suspicious
Signed SSD utility shows heavy obfuscation, suspicious sandbox behaviour (LSASS targeting, direct IP contact), but clean across 72 engines.
291e282a1574dda5ca…2c4362d15eThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
Zero detections from 72 engines including top tier-1 vendors provide a strong clean signal, but high-entropy packing, .NET Reactor obfuscation, and offensive MITRE techniques (T1562.001 via fsutil, T1620 timestomp) raise red flags. Heuristics highlight credential dumping shape and dropper profile, though the file is signed and has medium prevalence. No malicious runtime outcomes or external intel hits, but behaviour doesn't align with typical benign optimizers. Overall mixed signals warrant caution.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
0/72 engines malicious (17 tier1 clean: Avast, AVG, BitDefender, DrWeb, Emsisoft, ESET, F-Secure, Fortinet, GData, Ikarus, Kaspersky)
triggeredHeuristics 'MalwareTips.Synth.CredentialDumper' fired (evidence: lsass.exe)
behaviour.offensiveCount=3 (T1560, T1562.001, T1620); contactedIps[0]='162.159.36.2'
peAnalysis.likelyPacked=true; communityComments THOR 'SUSP_OBF_NET_Reactor_JIT_Encryption'
prevalence.classification='medium' (34 uniqueSources, 40 submissions)
- 0 malicious engines (17 tier1 clean: BitDefender, ESET, Kaspersky, etc.)
- Medium prevalence (40 submissions, 34 sources)
- No malicious sandbox verdict
- No dropped children or malicious hosts
- Signed executable
- High-entropy code and likely packing
- .NET Reactor obfuscation (cracked versions malware-linked)
- Offensive MITRE: T1562.001 (anti-forensic check), T1560, T1620
- LSASS targeting (Mimikatz-like)
- Direct IP C2 profile (162.159.36.2)
- Unknown signer 'Omid Soroori' (no history)
Treat as suspicious: do not execute unless verified from official source. Use sandbox or static analysis tools for confirmation; delete if unnecessary.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Tries to disable or bypass your security software.
High concern: Loads hidden code straight into memory to dodge scanners.
Moderate concern: Obfuscates or packs its code to avoid detection.
Moderate concern: Lists running programs — often to find security tools.
Moderate concern: Scans through your files and folders.
Moderate concern: Communicates over the network in a non-standard way.
Moderate concern: Unpacks hidden code only once it's running.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
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.
- 162.159.36.2
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- \Sessions\1\BaseNamedObjects
- \Device\KsecDD
- \\?\PIPE\lsarpc
- \\?\PIPE\NETLOGON
YARA & heuristic rule matches
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
Sandbox 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.exeSample contacted 1 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence162.159.36.2Unsigned, 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.
Evidence162.159.36.2
0 detections across 76 engines
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Forensic fingerprint
- File name
- SSDBooster.exe
- Size
- 3.38 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 291e282a1574dda5ca191a456d0c01f0defb69b2a4b18e2b4bbbdf2c4362d15e
- MD5
- 49f22135e2aa4a6abebc8cad0bc2ce07
- SHA-1
- 74f790636a883b9f7075a4988d9ee298c9da2852
- PE imphash
- f34d5f2d4577ed6d9ceec516c1f5a744
- First seen (VT)
- 1/27/2026, 3:09:17 PM
- Last analysis (VT)
- 2/11/2026, 1:14:56 AM
- First scan (MalwareTips)
- 4/21/2026, 2:13:31 PM
- Last scan (MalwareTips)
- 4/24/2026, 2:18:12 AM
- Code signer
- Omid Sorooriinvalid
Safety FAQ
Common questions about SSDBooster.exe, answered from the scan data above.
- SSDBooster.exe is suspicious — treat it as unsafe until you're sure. 0 of 76 antivirus engines flag it, which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- SSDBooster.exe is a Windows executable program, about 3.4 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- None — all 76 antivirus engines we queried report SSDBooster.exe as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove SSDBooster.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original SSDBooster.exe file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- SSDBooster.exe claims a signer of Omid Soroori, but the signature is not verified — an unverified or broken signature can be forged, so it should not be trusted as proof of who made the file.
- The SHA-256 hash of SSDBooster.exe is 291e282a1574dda5ca191a456d0c01f0defb69b2a4b18e2b4bbbdf2c4362d15e, and its MD5 is 49f22135e2aa4a6abebc8cad0bc2ce07. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on April 21, 2026. Because a file's hash never changes, the identity of SSDBooster.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.