GridinSoft Threat Intelligence

TrainerLib_x64.dll file report

Under review File reputation report
MD5 60a0ce176a0932f5d3079b8068c39604
Latest seen 2025-02-04 23:01:29 (a year ago)
First seen 2025-02-04 23:01:27 (a year ago)
Size 3 MB
Publisher WeMod LLC
Product WeMod
Signed by WeMod LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-02-04 23:01:27 (a year ago); latest analysis 2025-02-04 23:01:29 (a year ago).

Publisher context

Company metadata: WeMod LLC. Product metadata: WeMod.

Digital signature

Signed by WeMod LLC. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

File context

TrainerLib_x64.dll is a Windows file recorded in the ThreatInfo database. It is associated with WeMod. The reported company name is WeMod LLC. The current detection status is Undefined, based on the latest analysis from 2025-02-04 23:01:29 (a year ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

File Details

Product Name: WeMod
Company Name: WeMod LLC
MD5: 60a0ce176a0932f5d3079b8068c39604
Size: 3 MB
First Published: 2025-02-04 23:01:27 (a year ago)
Latest Published: 2025-02-04 23:01:29 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-04 23:01:29 (a year ago)

Overview

Signed By: WeMod LLC
Status: Valid

The signature on TrainerLib_x64.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

Common Places:

%localappdata%\squirreltemp\tempb\lib\net45\resources\app.asar.unpacked\static\unpacked
%localappdata%\squirreltemp\tempf\lib\net45\resources\app.asar.unpacked\static\unpacked
%localappdata%\squirreltemp\tempd\lib\net45\resources\app.asar.unpacked\static\unpacked

ThreatInfo has observed TrainerLib_x64.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 TrainerLib_x64.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Germany
Share 100.0%
Low High activity

The strongest geographic signal for this file is Germany 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:

Windows 10 100.0%

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

TrainerLib_x64.dll is identified as pe for 64-bit 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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x005f3058
Image base 0x0000000180000000

PE Sections:

Sections 12
Raw data 3648512

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

159232 bytes · 4.4% of section data
Uncommon name
MD5 c0a051e20470cd91cec5a2aa373ac2a2
46592 bytes · 1.3% of section data
Uncommon name
MD5 26a717ba041779f0bdcb4da749ea0c4b
1536 bytes · 0.0% of section data
Uncommon name
MD5 940f3d6398ee67f6764b2ffa1f94c949
9728 bytes · 0.3% of section data
Uncommon name
MD5 e0cc5ed3ac449012b1490818f604bbec
512 bytes · 0.0% of section data
Uncommon name
MD5 d38e9cb3eff003a869734c0f45864a2b
1024 bytes · 0.0% of section data
Uncommon name
MD5 203fa689afbf8d6765f69c619e66eb56
2048 bytes · 0.1% of section data
Uncommon name
MD5 891f21154856ba210aff0681e91cc585
.edata 512 bytes · 0.0% of section data
MD5 556edd4e80a3f65b0628e4d242fc0af6
.idata 512 bytes · 0.0% of section data
MD5 32fb8aca3a0c2f71cc6de039c3a20017
.rsrc 1536 bytes · 0.0% of section data
MD5 5d61e360c54a0620650718e3daa16517
.wemod 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 3425280 bytes · 93.9% of section data
Uncommon name
MD5 8da46c614b8dd17257f866cdc3f58126

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

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 60a0ce176a0932f5d3079b8068c39604.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.