oem-drv64.sys threat report

MD5 b0f6480014ebb24df6fe32e4fe412692
Latest seen 2024-08-29 23:01:16 (2 years ago)
First seen 2024-08-29 23:01:16 (2 years ago)
Size 41 KB
Publisher secr9tos

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2024-08-29 23:01:16 (2 years ago)
File hash
b0f6480014ebb24df6fe32e4fe412692
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2024-08-29 23:01:16 (2 years ago); latest analysis 2024-08-29 23:01:16 (2 years ago).

Publisher context

Company metadata: secr9tos. Product metadata: OEM-SLP2.1 ACPI Patch Driver (HPD64).

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

oem-drv64.sys is a Windows file recorded in the ThreatInfo database. It is associated with OEM-SLP2.1 ACPI Patch Driver (HPD64). The reported company name is secr9tos. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-08-29 23:01:16 (2 years ago).

If oem-drv64.sys appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: OEM-SLP2.1 ACPI Patch Driver (HPD64)
Company Name: secr9tos
MD5: b0f6480014ebb24df6fe32e4fe412692
Size: 41 KB
First Published: 2024-08-29 23:01:16 (2 years ago)
Latest Published: 2024-08-29 23:01:16 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-08-29 23:01:16 (2 years ago)
oem-drv64.sys detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%system%

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

100.0%

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

Windows 7 100.0%

The most common operating system signal for oem-drv64.sys is Windows 7 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.

oem-drv64.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000000010000
Entry Address: 0x0000fc88

PE Sections:

Name Size of data MD5
.text 2560 3e681a5e85558c948d2ae7b3aee009e2
seg0 15872 04ed40574172d0972ddd373267ca097e
.rdata 1024 c5462493f04fc8736218daf829d0b618
.data 512 043c46095689123e1f5be96c109c2f46
.pdata 512 f071ae42aed17b8421b7caa9920b041a
seg1 12800 5c9ac07953f8071f101f0ac5688abf57
seg2 512 5e8d0d0f87c22bf8f96f65956fc5fc43
PAGE 1024 59838ab69e587cd21b9bfb5aaf833b52
INIT 4608 115c25adb58f56852246a8302541e76b
.rsrc 1536 c0727927b06128908bec522ee1cd4de7
.reloc 512 699925c3478b0a8c4ca27bc9cc4b7209

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: