GridinSoft Threat Intelligence

Maticsoft.DBUtility.dll file report

Under review File reputation report
MD5 65bb6fffffaf195fe49dc9e382d31ba0
Latest seen 2021-06-10 20:37:52 (4 years ago)
First seen 2019-04-17 04:19:10 (7 years ago)
Size 71 KB
Publisher Maticsoft

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-04-17 04:19:10 (7 years ago); latest analysis 2021-06-10 20:37:52 (4 years ago).

Publisher context

Company metadata: Maticsoft. Product metadata: Maticsoft.DBUtility.

Digital signature

Signed by 北京文安卓立科技有限公司. 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.

Maticsoft.DBUtility.dll is a Windows file recorded in the ThreatInfo database. It is associated with Maticsoft.DBUtility. The reported company name is Maticsoft. The current detection status is Undefined, based on the latest analysis from 2021-06-10 20:37:52 (4 years 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.

Product Name: Maticsoft.DBUtility
Company Name: Maticsoft
MD5: 65bb6fffffaf195fe49dc9e382d31ba0
Size: 71 KB
First Published: 2019-04-17 04:19:10 (7 years ago)
Latest Published: 2021-06-10 20:37:52 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-10 20:37:52 (4 years ago)
Signed By: 北京文安卓立科技有限公司
Status: Valid

The signature on Maticsoft.DBUtility.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.

%programfiles%

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

Windows 8.1 50.0%
Windows 10 50.0%

The most common operating system signal for Maticsoft.DBUtility.dll is Windows 8.1 with 50.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.

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

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x0000e0de
Image base 0x11000000

.NET Info:

MVID: 01e6df35-3ebd-40a7-ac83-aeb4b1ad80ad

PE Sections:

Sections 3
Raw data 61440

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

.text 53248 bytes · 86.7% of section data
MD5 df02e87c2ab8c2909be2efff77bbc845
.rsrc 4096 bytes · 6.7% of section data
MD5 10ee627e46f8e00dd5f610e820915a53
.reloc 4096 bytes · 6.7% of section data
MD5 281f7925f9d347291a170591abfbd83c

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 65bb6fffffaf195fe49dc9e382d31ba0.
  • 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.