GridinSoft Threat Intelligence

ibtusb.sys file report

Under review File reputation report
MD5 18f7b1e3c5de1cc8b3d2bbf90f7350ef
Latest seen 2022-10-08 23:13:39 (3 years ago)
First seen 2022-10-08 23:13:39 (3 years ago)
Size 239 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-10-08 23:13:39 (3 years ago); latest analysis 2022-10-08 23:13:39 (3 years ago).

Digital signature

Signed by Intel(R) Wireless Connectivity Solutions;Microsoft Windows Hardware Compatibility Publisher. 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.

ibtusb.sys is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-10-08 23:13:39 (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.

MD5: 18f7b1e3c5de1cc8b3d2bbf90f7350ef
Size: 239 KB
First Published: 2022-10-08 23:13:39 (3 years ago)
Latest Published: 2022-10-08 23:13:39 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-10-08 23:13:39 (3 years ago)

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

%commonappdata%\reviversoft\driver reviver\downloads\57

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

ibtusb.sys 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 0x00015d98
Image base 0x0000000140000000

PE Sections:

Sections 8
Raw data 223744

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

.text 91648 bytes · 41.0% of section data
MD5 886e849857e70241c1fce93429e0ed86
.rdata 6656 bytes · 3.0% of section data
MD5 91f340090bcd60d316a545de4397bb92
.data 116224 bytes · 51.9% of section data
MD5 af6f05617d967ac961b5253c33d02b7a
.pdata 3072 bytes · 1.4% of section data
MD5 a987e9064a808428fa5a706667d92e5d
PAGE 1536 bytes · 0.7% of section data
Uncommon name
MD5 dd7b6ebd780a2586ccc82243b7bd1c6a
INIT 2048 bytes · 0.9% of section data
Uncommon name
MD5 4384e67baf5b27924675c494cf0341c2
.rsrc 2048 bytes · 0.9% of section data
MD5 bb1fb1f540da55ff6ddb5c7cf3b1c2eb
.reloc 512 bytes · 0.2% of section data
MD5 d067de1d402dfb4b7dd3f26df158fa25

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 18f7b1e3c5de1cc8b3d2bbf90f7350ef.
  • 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.