Should I block it?
No, this file is 100% safe to run.
Additional versions
Relationships
Parent process
Related files
PE file structure |
Show functions |
Export table
EurekaLog_PasswordRequestEvent
ExceptionManager
mylbx.exe
My Lockbox by FSPro Labs (Signed)
Version: | 2.8.7.393 |
MD5: | 723b1974a0de5ed158c062e5237cf7e7 |
SHA1: | 85c68bbae3e4f3b86d0bdb4b02728f18a1f10c37 |
SHA256: | c31d27ae141bc9868840805c0a9260faf3d3c1d3544d7db41f094fea059c92d8 |
Overview
mylbx.exe executes as a process with the local user's privileges usually within the context of Windows Explorer. It is set to be start when the PC boots and any user logs into Windows (added to the Run registry key for the all users under the local machine). This is typically installed with the program My Lockbox 2.9 published by FSPro Labs. The file is digitally signed by FSPro Labs which was issued by the VeriSign certificate authority (CA). Note, some antivirus scanners have flagged this file, however it is not necessarily considered malware (see below for details).
Details
File name: | mylbx.exe |
Publisher: | FSPro Labs |
Product name: | My Lockbox |
Typical file path: | C:\my lockbox\mylbx.exe |
File version: | 2.8.7.393 |
Product version: | 2.8.7 |
Size: | 2.11 MB (2,211,688 bytes) |
Certificate |
Issued to: | FSPro Labs |
Authority (CA): | VeriSign |
Expiration date: | Monday, February 10, 2014 |
Digital DNA |
File packed: | No |
.NET CLR: | No |
More details
Programs
The following program will install this file
“My Lockbox is a security software enabling you to password protect folders on your computer. The protected folder is hidden and locked from any user and application of your system and also from the net. To access the protected folder you have to provide a valid password. The program is extremely easy to use. You can protect the folder and set the password during the setup procedure. After the setup is finished, your folder will be hidde...”
Behaviors
Startup files (all users) run
Runs under the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run'
- 'mylbx' → C:\My Lockbox\mylbx.exe /a
Resource utilization
(Note: statistics below are averages based on a minimum sample size of 200 unique participants)
Averages
CPU |
Total CPU: | 0.00011660% | |
Kernel CPU: | 0.00000562% | |
User CPU: | 0.00011097% | |
Kernel CPU time: | 19,125 ms/min | |
CPU cycles: | 2,235,956/sec | |
Memory |
Private memory: | 12.32 MB | |
Private (maximum): | 18.74 MB | |
Private (minimum): | 17.67 MB | |
Non-paged memory: | 12.32 MB | |
Virtual memory: | 111.43 MB | |
Virtual memory (peak): | 132.6 MB | |
Working set: | 18.6 MB | |
Working set (peak): | 18.74 MB | |
Page faults: | 10,375/min | |
I/O |
I/O read transfer: | 33 Bytes/sec | |
I/O read operations: | 1/sec | |
I/O other transfer: | 408 Bytes/sec | |
I/O other operations: | 22/sec | |
Resource allocations |
Threads: | 5 | |
Handles: | 148 | |
GUI GDI count: | 149 | |
GUI GDI peak: | 151 | |
GUI USER count: | 90 | |
GUI USER peak: | 91 | |
Process properties
Threads
Averages
wow64.dll (Win32 Emulation on NT64 by Microsoft) |
Total CPU: | 0.02294786% | |
Kernel CPU: | 0.01262308% | |
User CPU: | 0.01032479% | |
CPU cycles: | 1,719,670/sec | |
Memory: | 252 KB | |
mylbx.exe (main module) |
Total CPU: | 0.00141743% | |
Kernel CPU: | 0.00082829% | |
User CPU: | 0.00058914% | |
CPU cycles: | 142,255/sec | |
Memory: | 3.53 MB | |
Common loaded modules
These are modules that are typiclaly loaded within the context of this process.
Distribution by Windows OS
OS version | distribution |
Windows 7 Ultimate |
33.33% |
|
Windows Vista Home Premium |
16.67% |
|
Windows Developer Preview |
16.67% |
|
Windows 7 Professional |
16.67% |
|
Windows 7 Home Premium |
16.67% |
|
Distribution by country
United States installs about 50.00% of My Lockbox.
Distribution by PC manufacturer
PC Manufacturer | distribution |
Dell |
33.33% |
|
Lenovo |
33.33% |
|
Hewlett-Packard |
33.33% |
|