GridinSoft Threat Intelligence

drvsrc.dll file report

Under review File reputation report
MD5 ac416d56af10a5b1a474dfec54a5ddc2
Latest seen 2022-08-30 23:20:34 (3 years ago)
First seen 2018-08-20 15:03:45 (7 years ago)
Size 254 KB
Signed by OSTOTO CO. LIMITED

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-08-20 15:03:45 (7 years ago); latest analysis 2022-08-30 23:20:34 (3 years ago).

Digital signature

Signed by OSTOTO CO. LIMITED. 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.

drvsrc.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-08-30 23:20:34 (3 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.

MD5: ac416d56af10a5b1a474dfec54a5ddc2
Size: 254 KB
First Published: 2018-08-20 15:03:45 (7 years ago)
Latest Published: 2022-08-30 23:20:34 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-30 23:20:34 (3 years ago)
Signed By: OSTOTO CO. LIMITED
Status: Valid

The signature on drvsrc.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%\ostotosoft
%sysdrive%\windows.old\program files (x86)\ostotosoft
%appdata%\zhp\quarantine\zhpcleaner\ostotosoft\ostotosoft
%appdata%\zhp\quarantine\zhpcleaner\ostotosoft

ThreatInfo has observed drvsrc.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 10 70.8%
Windows 7 18.5%
Windows 8.1 10.8%

The most common operating system signal for drvsrc.dll is Windows 10 with 70.8% 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.

drvsrc.dll is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x0001d4d1
Image base 0x10000000

PE Sections:

Sections 5
Raw data 243712

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

.text 171520 bytes · 70.4% of section data
MD5 1ff521d937a0fbc3ab81dced48b08ba8
.rdata 53248 bytes · 21.8% of section data
MD5 9770e38a13fb615b02b4d430d0e2ed2c
.data 5632 bytes · 2.3% of section data
MD5 470eb6079b70337e80dcec05ad58b8a9
.rsrc 1024 bytes · 0.4% of section data
MD5 3d540d397148594283581950bd224331
.reloc 12288 bytes · 5.0% of section data
MD5 155ed7db0515d98e79fa4e17237d29f8

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 ac416d56af10a5b1a474dfec54a5ddc2.
  • 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.