GridinSoft Threat Intelligence

lsass.exb file report

Clean record File reputation report
MD5 28f844500ada77447835bc586f15aaae
Latest seen 2021-01-10 14:50:32 (5 years ago)
First seen 2017-05-22 10:20:39 (8 years ago)
Size 56 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-22 10:20:39 (8 years ago); latest analysis 2021-01-10 14:50:32 (5 years ago).

Digital signature

Signed by Microsoft Windows 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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

lsass.exb is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-01-10 14:50:32 (5 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

MD5: 28f844500ada77447835bc586f15aaae
Size: 56 KB
First Published: 2017-05-22 10:20:39 (8 years ago)
Latest Published: 2021-01-10 14:50:32 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-10 14:50:32 (5 years ago)
Signed By: Microsoft Windows Publisher
Status: Valid

The signature on lsass.exb 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%\net protector\nposfile\2017-04-15_1628\files
%commonappdata%\net protector\nposfile\2017-02-25_2100\files
%sysdrive%\zv\noexp\files
%commonappdata%\net protector\nposfile\2018-05-03_0035
%commonappdata%\net protector\nposfile\2017-04-19_1055
%commonappdata%\net protector\nposfile\2017-06-06_0928

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

lsass.exb is identified as pe for 64-bit systems. The subsystem is Windows GUI. 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 Windows GUI
Entry point 0x00004710
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 47616

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

.text 19456 bytes · 40.9% of section data
MD5 a4a266384335e195d6db17697cdad35c
.rdata 22016 bytes · 46.2% of section data
MD5 688752eef54b8af7035a468c3a0247f0
.data 512 bytes · 1.1% of section data
MD5 781983918d9d279c1617828c31082ad2
.pdata 2048 bytes · 4.3% of section data
MD5 d6edf6c847ba9e10012428697bcbc2ef
.didat 512 bytes · 1.1% of section data
Uncommon name
MD5 03f4ec7011c1aec5d860860d550bc8fe
.rsrc 2048 bytes · 4.3% of section data
MD5 179eb344198076d28a94734001c69f43
.reloc 1024 bytes · 2.2% of section data
MD5 00eba1b2d26ef5d0caf68f9c0b53d8ab

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 28f844500ada77447835bc586f15aaae.
  • 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.