relay.dll threat report

MD5 7d2f87123e63950159fb2c724e55bdab
Latest seen 2026-01-30 23:01:16 (4 months ago)
First seen 2024-04-08 23:00:50 (2 years ago)
Size 1 MB
Publisher CANON INC.
Product relay.dll

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Downloader. 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.Downloader
Recommended action
Scan and remove
Last analysis
2026-01-30 23:01:16 (4 months ago)
File hash
7d2f87123e63950159fb2c724e55bdab
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Downloader.

Timeline

First seen 2024-04-08 23:00:50 (2 years ago); latest analysis 2026-01-30 23:01:16 (4 months ago).

Publisher context

Company metadata: CANON INC.. Product metadata: relay.dll.

Observed locations

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

  1. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

relay.dll is a Windows file recorded in the ThreatInfo database. It is associated with relay.dll. The reported company name is CANON INC.. The current detection status is Trojan.Downloader, based on the latest analysis from 2026-01-30 23:01:16 (4 months ago).

If relay.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.Downloader.

Product Name: relay.dll
Company Name: CANON INC.
MD5: 7d2f87123e63950159fb2c724e55bdab
Size: 1 MB
First Published: 2024-04-08 23:00:50 (2 years ago)
Latest Published: 2026-01-30 23:01:16 (4 months ago)
Status: Trojan.Downloader (on last analysis)
Analysis Date: 2026-01-30 23:01:16 (4 months ago)
relay.dll 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.

%appdata%
%appdata%
%appdata%
%profile%\downloads
%programfiles%
%appdata%
%appdata%
%appdata%
%appdata%
%appdata%

ThreatInfo has observed relay.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.

30.0%
20.0%
20.0%
10.0%
10.0%
10.0%

The strongest geographic signal for this file is Germany with 30.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for relay.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.

relay.dll is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x000f3084

PE Sections:

Name Size of data MD5
.text 1137664 d94288d3650d2343334727f5d3d9f7bd
.rdata 267264 bba957772f7e2e26e8c27b41b6d74aab
.data 23040 f3bef899bd317d8a9aa1ee5ab065ed2b
.rsrc 1536 bfe53defdd1c1072e73cb1f041e08440
.reloc 165888 3fa9df26dbe089ec74e22017b61f2401

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.

More information: