GridinSoft Threat Intelligence

ToolkitPro2200vc170U.dll file report

Under review File reputation report
MD5 cb3d9b5b2496ecaf1e2cbcfadfd614a9
Latest seen 2026-01-06 23:00:48 (4 months ago)
First seen 2026-01-06 23:00:48 (4 months ago)
Size 810 MB
Publisher Codejock Software

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-01-06 23:00:48 (4 months ago); latest analysis 2026-01-06 23:00:48 (4 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.

ToolkitPro2200vc170U.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 2026-01-06 23:00:48 (4 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: cb3d9b5b2496ecaf1e2cbcfadfd614a9
Size: 810 MB
First Published: 2026-01-06 23:00:48 (4 months ago)
Latest Published: 2026-01-06 23:00:48 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-06 23:00:48 (4 months ago)
%commonappdata%

ThreatInfo has observed ToolkitPro2200vc170U.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 100.0%

The most common operating system signal for ToolkitPro2200vc170U.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.

ToolkitPro2200vc170U.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 0x00005a94
Image base 0x67800000

PE Sections:

Sections 7
Raw data 11055104

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

.text 5580288 bytes · 50.5% of section data
Large raw data
MD5 00005271fbc469d64e19cba01e60d6da
.rdata 3949056 bytes · 35.7% of section data
MD5 978697f29a4cc681428d85cdaa8331b2
.data 188416 bytes · 1.7% of section data
MD5 c9e70778ed03d142fb3d030c47007f3c
.detourc 4608 bytes · 0.0% of section data
Uncommon name
MD5 b7009778727f76d8817191f0244ad11d
.detourd 512 bytes · 0.0% of section data
Uncommon name
MD5 15d7bd12d01a5e1cc9bcfda0df81f640
.rsrc 810496 bytes · 7.3% of section data
MD5 bdbff1e93811e7dc9d784189cb22224f
.reloc 521728 bytes · 4.7% of section data
MD5 881c1fb148b6a0bcd52ab4dc0d064771

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