GridinSoft Threat Intelligence

swdumon.sys#5E80C5B9A73DD4F4 file report

Under review File reputation report
MD5 04cf20310145dec63d5387beaff77d9a
Latest seen 2026-01-16 23:00:38 (4 months ago)
First seen 2017-05-21 10:03:10 (9 years ago)
Size 13 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2017-05-21 10:03:10 (9 years ago); latest analysis 2026-01-16 23:00:38 (4 months ago).

Digital signature

Signed by SlimWare Utilities Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

swdumon.sys#5E80C5B9A73DD4F4 is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2026-01-16 23:00:38 (4 months ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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.

MD5: 04cf20310145dec63d5387beaff77d9a
Size: 13 KB
First Published: 2017-05-21 10:03:10 (9 years ago)
Latest Published: 2026-01-16 23:00:38 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-16 23:00:38 (4 months ago)
Signed By: SlimWare Utilities Inc.
Status: Valid

The signature on swdumon.sys#5E80C5B9A73DD4F4 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.

%system%\drivers
%localappdata%\slimware utilities inc\driverupdate
%sysdrive%\adwcleaner\quarantine\files\qjguloenjciiqvawkhnlzbwfxspbegeb\driverupdate
%sysdrive%\adwcleaner\quarantine\files
%localappdata%\slimware utilities inc\slimdrivers
%sysdrive%\adwcleaner\quarantine\files\xhoyfsdreocoddooewpzbaxwwrygwlos\driverupdate
%sysdrive%\backsys\drivers
%sysdrive%\windows.old\windows\system32\drivers
%sysdrive%\adwcleaner\quarantine\files\jcluzlqdmuwuufkhmrxzuxlhsrstsvpd\driverupdate
%sysdrive%\windows.old\users\joendeb\appdata\local\slimware utilities inc\driverupdate

ThreatInfo has observed swdumon.sys#5E80C5B9A73DD4F4 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.

SWDUMon.sys sxwhumqdwjzvlgcyfqnvomexdoertypb.back SWDUMon(1970).sys SWDUMon.sys.vir tvikfaguhdtcnhkuagwbonttxvurfwcf.back SWDUMon (2016_02_02 16_13_06 UTC).sys SWDUMon (2016_01_30 17_41_52 UTC).sys SWDUMon (2016_01_27 19_22_39 UTC).sys SWDUMon (2015_12_14 17_34_13 UTC).sys SWDUMon (2015_12_16 12_15_29 UTC).sys SWDUMon (2015_12_16 22_22_42 UTC).sys SWDUMon (2015_12_13 14_45_42 UTC).sys SWDUMon (2015_12_07 13_34_29 UTC).sys $RYTGPZB.sys $RC8NLRF.sys SWDUMon(279).sys SWDUMon(2).sys qychdjblowdmcqxttwalyjeqsbyqumwh.back jynlwhyyoycupyxxfmllsmgkfkkadcij.back xxibreqbtjilmekvunjcspqesrwwznsk.back SWDUMon (2017_01_28 21_03_20 UTC).sys SWDUMon (2017_01_28 21_03_20 UTC).sys.quarantined SWDUMon (2017_06_26 00_08_18 UTC).sys.quarantined ejnjnrlehdlkvycgdoxwhzmtuxqvnbbe.back swdumon.sys#5E80C5B9A73DD4F4

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 10 68.5%
Windows 7 24.3%
Windows 8.1 5.8%
Windows 8 1.0%
Windows Vista 0.2%
Windows Embedded 8.1 0.1%

The most common operating system signal for swdumon.sys#5E80C5B9A73DD4F4 is Windows 10 with 68.5% 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.

swdumon.sys#5E80C5B9A73DD4F4 is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x00005008
Image base 0x0000000000010000

PE Sections:

Sections 5
Raw data 6144

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

.text 3584 bytes · 58.3% of section data
MD5 ad0944990bdca004670b1d6ad7b6e4af
.rdata 512 bytes · 8.3% of section data
MD5 e36dd966aa54337a8cce47483cf0b3c2
.data 512 bytes · 8.3% of section data
MD5 043c46095689123e1f5be96c109c2f46
.pdata 512 bytes · 8.3% of section data
MD5 88745a4e3437228ce5c5ee426a5e44ff
INIT 1024 bytes · 16.7% of section data
Uncommon name
MD5 d3ebe4b576a00f4b2259fc9e9fb02dc9

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 04cf20310145dec63d5387beaff77d9a.
  • 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. Use the PUP category to compare similar reports.