GridinSoft Threat Intelligence

amtransv.sys file report

Under review File reputation report
MD5 3acbd9a91478c8cdb1e04d717944d76c
Latest seen 2025-05-20 23:05:18 (a year ago)
First seen 2025-05-20 23:05:18 (a year ago)
Size 41 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-05-20 23:05:18 (a year ago); latest analysis 2025-05-20 23:05:18 (a year ago).

Publisher context

Company metadata: Windows (R) Codename Longhorn DDK provider. Product metadata: Windows (R) Codename Longhorn DDK driver.

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.

amtransv.sys is a Windows file recorded in the ThreatInfo database. It is associated with Windows (R) Codename Longhorn DDK driver. The reported company name is Windows (R) Codename Longhorn DDK provider. The current detection status is Undefined, based on the latest analysis from 2025-05-20 23:05:18 (a year 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: Windows (R) Codename Longhorn DDK driver
Company Name: Windows (R) Codename Longhorn DDK provider
MD5: 3acbd9a91478c8cdb1e04d717944d76c
Size: 41 KB
First Published: 2025-05-20 23:05:18 (a year ago)
Latest Published: 2025-05-20 23:05:18 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-20 23:05:18 (a year ago)
%programfiles%\airmagnet inc

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

amtransv.sys is identified as pe for 32-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 32-bit
Subsystem Native
Entry point 0x0000c22d
Image base 0x00010000

PE Sections:

Sections 7
Raw data 41472

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

.text 24064 bytes · 58.0% of section data
MD5 8f0063eb9f046dca8685c805242dc822
.rdata 1024 bytes · 2.5% of section data
MD5 278072f9a8e38163c09f8d4d2f412473
.data 8704 bytes · 21.0% of section data
MD5 3f4eea73e49df142945b8e81fb38c89a
PAGE 1536 bytes · 3.7% of section data
Uncommon name
MD5 73cf97c93d1c1e8d1ae619c138d2888d
INIT 2560 bytes · 6.2% of section data
Uncommon name
MD5 3a1b3c565ed01b14018315369714f345
.rsrc 1536 bytes · 3.7% of section data
MD5 10605cc9804b23f59550b7c1685afe76
.reloc 2048 bytes · 4.9% of section data
MD5 8824f9f020dd793da926a0f7694b80e1

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 3acbd9a91478c8cdb1e04d717944d76c.
  • 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.