GridinSoft Threat Intelligence

ToolkitPro1730vc140.dll file report

Under review File reputation report
MD5 284781664345c61fd375d013959e029b
Latest seen 2025-11-15 23:01:08 (6 months ago)
First seen 2018-04-27 14:07:28 (8 years ago)
Size 10 MB
Publisher Codejock Software

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-04-27 14:07:28 (8 years ago); latest analysis 2025-11-15 23:01:08 (6 months ago).

Publisher context

Company metadata: Codejock Software. Product metadata: Xtreme Toolkit Pro™ Dynamic Link Library.

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.

ToolkitPro1730vc140.dll is a Windows file recorded in the ThreatInfo database. It is associated with Xtreme Toolkit Pro™ Dynamic Link Library. The reported company name is Codejock Software. The current detection status is Undefined, based on the latest analysis from 2025-11-15 23:01:08 (6 months 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: Xtreme Toolkit Pro™ Dynamic Link Library
Company Name: Codejock Software
MD5: 284781664345c61fd375d013959e029b
Size: 10 MB
First Published: 2018-04-27 14:07:28 (8 years ago)
Latest Published: 2025-11-15 23:01:08 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-15 23:01:08 (6 months ago)
%programfiles%

ThreatInfo has observed ToolkitPro1730vc140.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 80.0%
Windows 7 20.0%

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

ToolkitPro1730vc140.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 0x0053233e
Image base 0x67800000

PE Sections:

Sections 7
Raw data 10997760

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

.text 5881344 bytes · 53.5% of section data
Large raw data
MD5 580e463aa8656f89034b0d324fad1fd9
.rdata 3615232 bytes · 32.9% of section data
MD5 afcceb0142c35699880fd87bdb43a08f
.data 143872 bytes · 1.3% of section data
MD5 8ca582cb14240069de05cbafd11a61ed
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 ee4293a7a2a044924bd4ee5d7145fcd1
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 857600 bytes · 7.8% of section data
MD5 cc596e21930c943deccbd4eb4ef5f70c
.reloc 498688 bytes · 4.5% of section data
MD5 d6870127bb446885032ad5fb4a45a966

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 284781664345c61fd375d013959e029b.
  • 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.