GridinSoft Threat Intelligence
Riched32.dll threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.
- Detection name
- Trojan.Heur!
- Recommended action
- Scan and remove
- Last analysis
- 2021-11-03 21:59:09 (4 years ago)
- File hash
- 33684a8fde3c50475da1f740fd656e95
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Trojan.Heur!.
First seen 2021-11-03 21:59:09 (4 years ago); latest analysis 2021-11-03 21:59:09 (4 years ago).
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
Riched32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Missive. The reported company name is Missive. The current detection status is Trojan.Heur!, based on the latest analysis from 2021-11-03 21:59:09 (4 years ago).
If Riched32.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.
File Details
| Product Name: | Missive |
| Company Name: | Missive |
| MD5: | 33684a8fde3c50475da1f740fd656e95 |
| Size: | 5 MB |
| First Published: | 2021-11-03 21:59:09 (4 years ago) |
| Latest Published: | 2021-11-03 21:59:09 (4 years ago) |
| Status: | Trojan.Heur! (on last analysis) | |
| Analysis Date: | 2021-11-03 21:59:09 (4 years ago) |
Detection screenshot
The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.
Common Places:
| %system%\fr-ca |
ThreatInfo has observed Riched32.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen Riched32.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Indonesia with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for Riched32.dll is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
Riched32.dll is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d41d8cd98f00b204e9800998ecf8427e
d41d8cd98f00b204e9800998ecf8427e
d41d8cd98f00b204e9800998ecf8427e
d41d8cd98f00b204e9800998ecf8427e
ffab9a9dc106f9f60997c479d6c80462
02d802b653155e53f1026a037a48a2e0
1cf9e008a7790e2794fd4d103f387b6e
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
GridinSoft detects this file as Trojan.Heur!
This report identifies Riched32.dll by MD5 33684a8fde3c50475da1f740fd656e95. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.