maple.dll threat report

MD5 5b31443f24e062b09070d5b1e6da8496
Latest seen 2025-12-25 23:01:01 (5 months ago)
First seen 2025-12-25 23:01:01 (5 months ago)
Size 7 MB
Publisher Maplesoft
Product maplelmg.exe

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
2025-12-25 23:01:01 (5 months ago)
File hash
5b31443f24e062b09070d5b1e6da8496
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2025-12-25 23:01:01 (5 months ago); latest analysis 2025-12-25 23:01:01 (5 months ago).

Publisher context

Company metadata: Maplesoft. Product metadata: maplelmg.exe.

Digital signature

Signed by Waterloo Maple Inc.. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

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.

maple.dll is a Windows file recorded in the ThreatInfo database. It is associated with maplelmg.exe. The reported company name is Maplesoft. The current detection status is Trojan.Heur!, based on the latest analysis from 2025-12-25 23:01:01 (5 months ago).

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

Product Name: maplelmg.exe
Company Name: Maplesoft
MD5: 5b31443f24e062b09070d5b1e6da8496
Size: 7 MB
First Published: 2025-12-25 23:01:01 (5 months ago)
Latest Published: 2025-12-25 23:01:01 (5 months ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2025-12-25 23:01:01 (5 months ago)
maple.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.

Signed By: Waterloo Maple Inc.
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on maple.dll is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%programfiles%\maple 2024

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

maple.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: 0x00522ea0

PE Sections:

Name Size of data MD5
.text 5392896 6de24dd5375e07cb5883d0fd5ed0ada7
.textidx 1166848 e4cf9958fd850cfdb066ace338b901db
jkl.text 139776 07a5fccbcd6e733239065e21202de721
jkl.bss 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 915968 3aab8a4692468028662b8d3c36c5a189
.data 237568 729a12d59b6c06866112e4073bef46be
.pdata 118784 32c4c5ca6f12be394b91748f999ba936
jkl.xdat 17408 4cf2e8dd274725fba7a47af1508fb3de
jkl.pdat 11776 6d10cb56bbc078c370485f84026c458c
jkl.data 1024 92029d842a5f938b44595e82fc4bf516
jkl.rdat 11264 8cbb133651835a8493dc0c86fb907da6
_RDATA 4608 0a8f29a5710b7fc87a851fe93bed4ec0
.rsrc 1536 16ef4701c392ccd61183617227bb860f
.reloc 23552 84e5b9e31b2504a3ce9181465aabeab3

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: