Suspicious
Unsigned executable showing process-injection behaviour and direct-IP contact with no AV detections.
9d77a8afb5551e452d…faff281f4dThe 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 73 reporting engines including 18 tier-1 engines is a strong clean signal, but the file is unsigned and exhibits T1055 process injection plus direct-IP C2 patterns that malware commonly uses. The 4081-day age and medium prevalence suggest the binary has circulated for years without widespread detection, yet the behavioural heuristics remain unrefuted by any engine consensus. This leaves the sample in a borderline state where neither malicious nor safe classification is strongly supported.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.malicious=0 and engines.tier1Malicious=0 across 73 reporting engines
behaviour.offensiveTechniques=["T1055"] and triggeredHeuristics[0].rule="MalwareTips.Synth.ProcessInjection"
behaviour.contactedIps=["20.99.184.37","20.99.133.109"] with zero contactedDomains
signing.verified=false and prevalence.classification=medium
- Zero detections from 73 engines
- No tier-1 malicious labels
- No malicious sandbox verdicts
- Unsigned PE
- T1055 process injection observed
- Direct IP contact without DNS
Treat as untrusted until additional context or code review confirms its purpose; isolate execution and monitor network activity.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Hides inside another running program to evade antivirus.
High concern: Records what you type — keylogger behaviour.
Moderate concern: Connects out to 3 servers on the internet.
Note: Collects details about your system.
Note: Loads extra code modules while 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.
- 20.99.184.37
- a83f:8110:0:0:100:0:0:0
- 20.99.133.109
- \Device\ConDrv\\Connect
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF174.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF23F.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF26F.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERB26.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERB28.tmp.csv
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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence%SAMPLEPATH%\9d77a8afb5551e452d802531afdd1b5784588b910831bfcd84be1cfaff281f4d.exeSample contacted 3 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.
Evidence20.99.184.37 · a83f:8110:0:0:100:0:0:0 · 20.99.133.109
0 detections across 77 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Forensic fingerprint
- File name
- filtdump.exe
- Size
- 46.0 KB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 9d77a8afb5551e452d802531afdd1b5784588b910831bfcd84be1cfaff281f4d
- MD5
- 238eab2029c6aff0f51eb04abd32b44a
- SHA-1
- d4f351561fba51c03adcde70b636e4f18163c571
- PE imphash
- e5165cd6eff43d3c9c77207844b430d7
- First seen (VT)
- 5/15/2015, 2:36:12 PM
- Last analysis (VT)
- 3/19/2025, 6:41:46 AM
- First scan (MalwareTips)
- 7/17/2026, 11:43:50 PM
- Last scan (MalwareTips)
- 7/17/2026, 11:43:50 PM
Safety FAQ
Common questions about filtdump.exe, answered from the scan data above.
- filtdump.exe is suspicious — treat it as unsafe until you're sure. 0 of 77 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.
- filtdump.exe is a Windows executable program, about 46 KB. 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 77 antivirus engines we queried report filtdump.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 filtdump.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 filtdump.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.
- The SHA-256 hash of filtdump.exe is 9d77a8afb5551e452d802531afdd1b5784588b910831bfcd84be1cfaff281f4d, and its MD5 is 238eab2029c6aff0f51eb04abd32b44a. 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 July 17, 2026. Because a file's hash never changes, the identity of filtdump.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.