isafekrnlr3.sys file report

MD5 821fc895831b719afa0d5d2be2027893
Latest seen 2023-07-26 23:44:42 (2 years ago)
First seen 2017-05-21 05:04:31 (8 years ago)
Size 71 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 05:04:31 (8 years ago); latest analysis 2023-07-26 23:44:42 (2 years ago).

Publisher context

Company metadata: Elex do Brasil Participações Ltda. Product metadata: YAC Security Protection.

Digital signature

Signed by Elex do Brasil Participações Ltda. 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.

isafekrnlr3.sys is a Windows file recorded in the ThreatInfo database. It is associated with YAC Security Protection. The reported company name is Elex do Brasil Participações Ltda. The current detection status is Undefined, based on the latest analysis from 2023-07-26 23:44:42 (2 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.

Product Name: YAC Security Protection
Company Name: Elex do Brasil Participações Ltda
MD5: 821fc895831b719afa0d5d2be2027893
Size: 71 KB
First Published: 2017-05-21 05:04:31 (8 years ago)
Latest Published: 2023-07-26 23:44:42 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-07-26 23:44:42 (2 years ago)
Signed By: Elex do Brasil Participações Ltda
Status: Valid

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

%programfiles%\elex-tech\yac
%temp%\ist5332.tmp\sys\x86
%temp%\istcc09.tmp\sys\x86
%temp%\istca6f.tmp\sys\x86
%temp%\ist4161.tmp\sys\x86
%temp%\istdc68.tmp\sys\x86
%temp%\isteda.tmp\sys\x86
%temp%\ist955b.tmp\sys\x86
%temp%\ist131b.tmp\sys\x86
%sysdrive%\system volume information\_restore{f14a1c2c-a641-43f9-a293-b0cb265a4677}\rp1227

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

iSafeKrnlR3.sys
A0422265.sys
A0428002.sys
trz80A1.tmp
A0096131.sys
isafekrnlr3.sys

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.

36.5%
8.2%
7.7%
7.3%
7.3%
7.3%
3.9%
3.0%
2.6%
2.6%
1.7%
1.3%
1.3%
0.9%
0.9%
0.9%
0.9%
0.9%
0.9%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%

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

Windows 7 74.8%
Windows 10 10.7%
Windows XP 9.4%
Windows 8 2.6%
Windows 8.1 2.1%
Windows Vista 0.4%

The most common operating system signal for isafekrnlr3.sys is Windows 7 with 74.8% 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.

isafekrnlr3.sys is identified as pe for 32 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: 32
Image Base: 0x00010000
Entry Address: 0x0000c2be

PE Sections:

Name Size of data MD5
.text 33152 272c18fd8f388f249d8ebc302e0b86d1
.data 9088 6f1d301cc8107d55e641595968ad9ea5
PAGE 6400 3e3dcc523386746961a3a27928028299
INIT 2048 640d0eeb2ec9ce40420059fdb20de24c
.rsrc 1024 2719e3cccff3c97da93995838e18081f
.reloc 2688 fc82229f1eb5a9a683132e3f3a6049f0

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: