Suspicious
Zero engine detections but rare new file shows process injection behaviour under a signer with mixed prior verdicts.
195a32ad77ed5afbac…f2f55e589cThe 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 69 reporting engines including 16 tier-1 engines rules out widespread malicious consensus. The signer 'Open Text Corporation' has four prior safe verdicts on similar files. However the file is only 10 days old, has no signer history in our database, and the sandbox recorded T1055 process injection plus T1562.001 evasion. These offensive techniques plus the rare_new prevalence classification create mixed signals that prevent a clean safe verdict.
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, tier1Malicious=0 across 69 reporting engines
signing.verified=true, signer='Open Text Corporation'
similarHashes[1].verdict=safe (matchKind=signer, reason=ai:benign_signed_installer)
triggeredHeuristics[0].rule=MalwareTips.Synth.ProcessInjection (T1055 observed)
prevalence.classification=rare_new, firstSubmissionDate=2026-07-08
- 0/73 engines flagged malicious
- signed and verified by Open Text Corporation
- 4 of 5 similar signer files previously rated safe
- no malicious sandbox verdict or dropped children
- rare_new prevalence (1 submission)
- T1055 process injection observed
- T1562.001 defence-evasion technique
- no prior signer history in database
Treat as untrusted until additional behavioural or code-signing telemetry is available; do not deploy in production without further review.
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.
High concern: Downloads more malware onto your PC.
High concern: Tries to disable or bypass your security software.
High concern: Hijacks how Windows loads programs so it runs automatically.
Moderate concern: Obfuscates or packs its code to avoid detection.
Moderate concern: Runs hidden system commands (script or shell).
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.
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\executable.exe.log
- \Device\ConDrv
- \Device\ConDrv\\Connect
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- d8988d672d6915b46946…cc146bNever scannednever seen before
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\executable.exe"
0 detections across 73 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
Barely seen in the wild and first surfaced recently. This is the footprint of targeted malware the AV industry hasn't signatured yet — extra scrutiny is warranted.
Forensic fingerprint
- File name
- PDFParser.exe
- Size
- 17.5 KB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 195a32ad77ed5afbac36a8d75f1a581e33b970ac9a35715a874705f2f55e589c
- MD5
- 913903da6385993668e6aad62ced3bba
- SHA-1
- 0fe9cbccda81222703c45d03cad955f1aeaa0346
- PE imphash
- f34d5f2d4577ed6d9ceec516c1f5a744
- First seen (VT)
- 7/8/2026, 11:22:27 AM
- Last analysis (VT)
- 7/8/2026, 11:22:27 AM
- First scan (MalwareTips)
- 7/17/2026, 11:46:24 PM
- Last scan (MalwareTips)
- 7/17/2026, 11:46:24 PM
- Code signer
- Open Text Corporationverified
Safety FAQ
Common questions about PDFParser.exe, answered from the scan data above.
- PDFParser.exe is suspicious — treat it as unsafe until you're sure. 0 of 73 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.
- PDFParser.exe is a Windows executable program, about 17 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 73 antivirus engines we queried report PDFParser.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 PDFParser.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 PDFParser.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.
- Yes — PDFParser.exe carries a valid digital signature from Open Text Corporation, which confirms the file hasn't been tampered with since that publisher signed it. A valid signature is a positive signal, but note that malware is occasionally signed with stolen or abused certificates, so it isn't proof of safety on its own.
- The SHA-256 hash of PDFParser.exe is 195a32ad77ed5afbac36a8d75f1a581e33b970ac9a35715a874705f2f55e589c, and its MD5 is 913903da6385993668e6aad62ced3bba. 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 PDFParser.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.