GridinSoft Threat Intelligence
oem-drv86.sys threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Hack.AutoKMS. 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
- Hack.AutoKMS
- Recommended action
- Scan and remove
- Last analysis
- 2025-02-22 23:01:35 (a year ago)
- File hash
- fb1c2fd15bf77e0e08eb5b71e179de80
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Hack.AutoKMS.
First seen 2017-05-25 09:03:48 (8 years ago); latest analysis 2025-02-22 23:01:35 (a year ago).
Company metadata: secr9tos. Product metadata: OEM-SLP2.1 ACPI Patch Driver (HPD86).
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
oem-drv86.sys is a Windows file recorded in the ThreatInfo database. It is associated with OEM-SLP2.1 ACPI Patch Driver (HPD86). The reported company name is secr9tos. The current detection status is Hack.AutoKMS, based on the latest analysis from 2025-02-22 23:01:35 (a year ago).
If oem-drv86.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 Hack.AutoKMS.
File Details
| Product Name: | OEM-SLP2.1 ACPI Patch Driver (HPD86) |
| Company Name: | secr9tos |
| MD5: | fb1c2fd15bf77e0e08eb5b71e179de80 |
| Size: | 8 KB |
| First Published: | 2017-05-25 09:03:48 (8 years ago) |
| Latest Published: | 2025-02-22 23:01:35 (a year ago) |
| Status: | Hack.AutoKMS (on last analysis) | |
| Analysis Date: | 2025-02-22 23:01:35 (a year ago) |
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.
Common Places:
| %temp%\7zipsfx.001\bios_emulator |
| %windir%\kj\bios_emulator |
| %system%\drivers |
| %temp%\7zipsfx.000\bios_emulator |
| %sysdrive%\temp\7zipsfx.000\bios_emulator |
| %sysdrive%\windows.old\windows\kj\bios_emulator |
| %temp%\7zipsfx.002\bios_emulator |
| %temp%\7zipsfx.003\bios_emulator |
| %windir%\kj |
| %sysdrive%\0backup\program\k.j_130319\k.j_130319.exe |
ThreatInfo has observed oem-drv86.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.
File Names:
3 observed namesThis 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.
Geographic signal
Observed country distribution
ThreatInfo has seen oem-drv86.sys across 46 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Korea, Republic of with 20.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for oem-drv86.sys is Windows 7 with 58.7% 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.
Analysis
oem-drv86.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
0bc0cda3383877fa4de55b6be92f211d
2dcd12102946023c50643d31aea50ffd
83aaef3a426d8c7233ab63583d1fa00a
a1d151d8a801fa95e405c27c82ccb20f
80bb1429515120be3f282f4300bb9987
1d1a543c87f779d88eda45d8a989c8ed
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
GridinSoft detects this file as Hack.AutoKMS
This report identifies oem-drv86.sys by MD5 fb1c2fd15bf77e0e08eb5b71e179de80. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.