Custom.dll threat report

MD5 5b1a2737b093c9907fb184956b621d48
Latest seen 2024-02-28 23:55:43 (2 years ago)
First seen 2024-02-28 23:55:43 (2 years ago)
Size 3 MB
Publisher Online-Fix.Me

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
2024-02-28 23:55:43 (2 years ago)
File hash
5b1a2737b093c9907fb184956b621d48
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2024-02-28 23:55:43 (2 years ago); latest analysis 2024-02-28 23:55:43 (2 years ago).

Publisher context

Company metadata: Online-Fix.Me.

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.

Custom.dll is a Windows file recorded in the ThreatInfo database. The reported company name is Online-Fix.Me. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-02-28 23:55:43 (2 years ago).

If Custom.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!.

Company Name: Online-Fix.Me
MD5: 5b1a2737b093c9907fb184956b621d48
Size: 3 MB
First Published: 2024-02-28 23:55:43 (2 years ago)
Latest Published: 2024-02-28 23:55:43 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-02-28 23:55:43 (2 years ago)
Custom.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.

%profile%\downloads\games\the quarry bypass\smg026\binaries

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

100.0%

The strongest geographic signal for this file is Brazil with 100.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 Custom.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.

Custom.dll is identified as pe for 64 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: 64
Image Base: 0x0000000180000000
Entry Address: 0x003b91dc

PE Sections:

Name Size of data MD5
.text 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 0 d41d8cd98f00b204e9800998ecf8427e
.data 0 d41d8cd98f00b204e9800998ecf8427e
.pdata 0 d41d8cd98f00b204e9800998ecf8427e
_RDATA 0 d41d8cd98f00b204e9800998ecf8427e
.of0 0 d41d8cd98f00b204e9800998ecf8427e
.of1 1536 f9c9cc95b92ea6a598297d2e34409b2a
.of2 3604992 3cfecbca5486d16a23916bc1d207fc6b
.reloc 512 415bb3ec7412bc9dea6769b3912e5147
.rsrc 1024 a04d1272ed8fa4ae18cd4806cffa833c

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: