GridinSoft Threat Intelligence

DOCSchedule.exe file report

Under review File reputation report
MD5 7357aac4410684bd7a186e44135e36b0
Latest seen 2024-06-06 23:05:11 (2 years ago)
First seen 2024-04-22 23:01:29 (2 years ago)
Size 3 MB
Publisher Solvusoft Corporation
Product DriverDoc Schedule
Signed by Solvusoft Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-04-22 23:01:29 (2 years ago); latest analysis 2024-06-06 23:05:11 (2 years ago).

Publisher context

Company metadata: Solvusoft Corporation. Product metadata: DriverDoc Schedule.

Digital signature

Signed by Solvusoft Corporation. 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

DOCSchedule.exe is a Windows file recorded in the ThreatInfo database. It is associated with DriverDoc Schedule. The reported company name is Solvusoft Corporation. The current detection status is Undefined, based on the latest analysis from 2024-06-06 23:05:11 (2 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.

File Details

Product Name: DriverDoc Schedule
Company Name: Solvusoft Corporation
MD5: 7357aac4410684bd7a186e44135e36b0
Size: 3 MB
First Published: 2024-04-22 23:01:29 (2 years ago)
Latest Published: 2024-06-06 23:05:11 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-06-06 23:05:11 (2 years ago)

Overview

Signed By: Solvusoft Corporation
Status: Valid

The signature on DOCSchedule.exe 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:

%sysdrive%\$recycle.bin\s-1-5-21-1685594058-1019298906-1066303956-1001\$r5jexpc
%programfiles%\driverdoc

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

Top country Ukraine
Share 50.0%
Low High activity

The strongest geographic signal for this file is Ukraine with 50.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 DOCSchedule.exe 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

DOCSchedule.exe 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 0x002c1ccc
Image base 0x00400000

PE Sections:

Sections 11
Raw data 3364864

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

.text 2874368 bytes · 85.4% of section data
MD5 98cd861cc0c0942b746a06b8c2e0dac9
.itext 14336 bytes · 0.4% of section data
Uncommon name
MD5 0066bc9936273978bf8fd1c982c8766b
.data 63488 bytes · 1.9% of section data
MD5 42278061594398ab7a28de149db2693f
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 18944 bytes · 0.6% of section data
MD5 14fadeaac349e2f23e0f4647e8f2fbc2
.didata 3072 bytes · 0.1% of section data
Uncommon name
MD5 4aa7a05e5dbb2627b14720576c2864bb
.edata 512 bytes · 0.0% of section data
MD5 a7863bce27ed20852a9286341f6e10da
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.0% of section data
MD5 ecb10141468b13ff49a4bad8b8e00cd6
.reloc 264704 bytes · 7.9% of section data
MD5 40a7221440135ee913b7e777ed676d8c
.rsrc 124928 bytes · 3.7% of section data
MD5 041d7c2f7db83fe16dd982d00ab20595

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 7357aac4410684bd7a186e44135e36b0.
  • 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.