CommonToolkit2.exe file report

MD5 3004e0d2ae0edc04cdf00860a8795869
Latest seen 2022-08-23 23:38:14 (3 years ago)
First seen 2019-03-06 15:33:51 (7 years ago)
Size 349 KB
Publisher SPAMfighter ApS
Signed by SPAMfighter ApS

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-03-06 15:33:51 (7 years ago); latest analysis 2022-08-23 23:38:14 (3 years ago).

Publisher context

Company metadata: SPAMfighter ApS. Product metadata: FULL-DISKfighter Service.

Digital signature

Signed by SPAMfighter ApS. 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.

CommonToolkit2.exe is a Windows file recorded in the ThreatInfo database. It is associated with FULL-DISKfighter Service. The reported company name is SPAMfighter ApS. The current detection status is Undefined, based on the latest analysis from 2022-08-23 23:38:14 (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.

Product Name: FULL-DISKfighter Service
Company Name: SPAMfighter ApS
MD5: 3004e0d2ae0edc04cdf00860a8795869
Size: 349 KB
First Published: 2019-03-06 15:33:51 (7 years ago)
Latest Published: 2022-08-23 23:38:14 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-23 23:38:14 (3 years ago)
Signed By: SPAMfighter ApS
Status: Valid

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

%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools
%commondir%\common toolkit suite\tools

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

36.4%
18.2%
9.1%
9.1%
9.1%
9.1%
9.1%

The strongest geographic signal for this file is Austria with 36.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 72.7%
Windows 8.1 18.2%
Windows 7 9.1%

The most common operating system signal for CommonToolkit2.exe is Windows 10 with 72.7% 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.

CommonToolkit2.exe is identified as pe for 64 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x00028738

PE Sections:

Name Size of data MD5
.text 181248 ceae377672930257c049a0b8d6b441a9
.rdata 101888 5ee207adc07409aee34589b32ac3a516
.data 15872 b09b3a1eb6312f8d4444b2ad19f85ed0
.pdata 16896 674f94cdbb538faf8759df3fa3867a83
.rsrc 31232 d46ead517821f5af7a502c4185ef9a5e
.reloc 4096 80a3668b049a584960e768028237285c

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.

More information: