GridinSoft Threat Intelligence

cnwOldXMLManager.exe file report

Clean record File reputation report
MD5 9976df9d15f52ed51f687c5102abaf5c
Latest seen 2026-01-21 23:00:57 (4 months ago)
First seen 2026-01-21 23:00:57 (4 months ago)
Size 187 KB
Signed by Canon Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2026-01-21 23:00:57 (4 months ago); latest analysis 2026-01-21 23:00:57 (4 months ago).

Publisher context

Product metadata: cnwOldXMLManager.exe.

Digital signature

Signed by Canon Inc.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

cnwOldXMLManager.exe is a Windows file recorded in the ThreatInfo database. It is associated with cnwOldXMLManager.exe. The current detection status is Clean, based on the latest analysis from 2026-01-21 23:00:57 (4 months ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: cnwOldXMLManager.exe
MD5: 9976df9d15f52ed51f687c5102abaf5c
Size: 187 KB
First Published: 2026-01-21 23:00:57 (4 months ago)
Latest Published: 2026-01-21 23:00:57 (4 months ago)
Status: Clean (on last analysis)
Analysis Date: 2026-01-21 23:00:57 (4 months ago)
Signed By: Canon Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%

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

Windows 10 100.0%

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

cnwOldXMLManager.exe is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x0000c2d8
Image base 0x00400000

PE Sections:

Sections 5
Raw data 180736

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

.text 112128 bytes · 62.0% of section data
MD5 1b44e4d2e1422493b5a9727613d22ec9
.rdata 51712 bytes · 28.6% of section data
MD5 e2ef0722c58949767f78c98e2f3679ee
.data 5632 bytes · 3.1% of section data
MD5 99f49b4d9f922fe4e96a32d7f48ac5da
.rsrc 1536 bytes · 0.8% of section data
MD5 da1fd6b89996255aceac34f8a17c4e81
.reloc 9728 bytes · 5.4% of section data
MD5 b3a9f154a2c5e13c37b62f976caea558

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 9976df9d15f52ed51f687c5102abaf5c.
  • 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.