Suspicious
Unsigned 12-year-old EXE shows process-injection and direct-IP C2 behaviour with zero AV detections.
3e806008db78d036bc…55f659e5f4The 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 malicious detections across 71 reporting engines rules out any tier-1 or named-family consensus. The unsigned status and absence of signer history remove the usual trust anchor. Two high-severity synthetic heuristics (T1055 injection and direct-IP C2) plus 15 raw IP contacts are classic malware indicators, yet the sandbox produced no malicious verdict and the file has survived 4282 days with only medium prevalence. These contradictory signals place the sample in the suspicious band.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines: 0 malicious detections, tier1Malicious=0, tier1FamilyConsensus absent
behaviour.offensiveTechniques=["T1055"], triggeredHeuristics=["MalwareTips.Synth.ProcessInjection", "MalwareTips.Synth.DirectIpC2"]
signing.verified=false, signerStats.found=false
prevalence.classification=medium, ageDays=4282, similarHashes.length=0
- Zero engine detections
- No malicious sandbox verdict
- Medium prevalence over 12 years
- Unsigned executable
- T1055 process injection observed
- 15 direct-IP contacts, zero DNS
Treat as untrusted; execute only under controlled conditions and monitor network activity to the observed IPs.
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: Talks to a remote server to take commands or send out your data.
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.
- a83f:8110:4300:5000:5600:3600:2d00:4f00
- 23.216.147.76
- 23.216.147.64
- 20.99.133.109
- 20.99.184.37
- 20.99.185.48
- 192.229.211.108
- a83f:8110:0:0:100:0:1800:0
- 192.168.0.55
- 23.216.81.152
- \Device\ConDrv\\Connect
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC6E.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1A.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD4A.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER125B.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER125C.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"C:\Users\<USER>\Desktop\software.exe"Sample contacted 15 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.
Evidencea83f:8110:4300:5000:5600:3600:2d00:4f00 · 23.216.147.76 · 23.216.147.64
0 detections across 75 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
- 45.0 KB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 3e806008db78d036bcd47000c6679ea87f6e0ccf1177d5d6e764db55f659e5f4
- MD5
- 767036e5642c6cbbf16177052bb3ed01
- SHA-1
- 11c951c48722099708e9f1145baac1b2798dfde2
- PE imphash
- 44095388cb9f5eee93661305a29e8999
- First seen (VT)
- 10/27/2014, 9:06:46 AM
- Last analysis (VT)
- 6/9/2026, 7:04:29 AM
- First scan (MalwareTips)
- 7/17/2026, 11:43:03 PM
- Last scan (MalwareTips)
- 7/17/2026, 11:43:03 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 75 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 45 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 75 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 3e806008db78d036bcd47000c6679ea87f6e0ccf1177d5d6e764db55f659e5f4, and its MD5 is 767036e5642c6cbbf16177052bb3ed01. 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.