GridinSoft Threat Intelligence
TabProtect_Scheduler.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2020-06-21 17:19:28 (5 years ago); latest analysis 2021-03-28 20:27:11 (5 years ago).
Company metadata: Auslo?gics. Product metadata: BoostS?peed.
Signed by Auslogics Labs Pty Ltd. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
TabProtect_Scheduler.dll is a Windows file recorded in the ThreatInfo database. It is associated with BoostS?peed. The reported company name is Auslo?gics. The current detection status is Undefined, based on the latest analysis from 2021-03-28 20:27:11 (5 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.
File Details
| Product Name: | BoostS?peed |
| Company Name: | Auslo?gics |
| MD5: | f540f91df6385af93c088cf04fc423ca |
| Size: | 607 KB |
| First Published: | 2020-06-21 17:19:28 (5 years ago) |
| Latest Published: | 2021-03-28 20:27:11 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-03-28 20:27:11 (5 years ago) |
Overview
| Signed By: | Auslogics Labs Pty Ltd |
| Status: | Valid |
The signature on TabProtect_Scheduler.dll 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.
Common Places:
| %programfiles%\auslogics |
| %programfiles% |
ThreatInfo has observed TabProtect_Scheduler.dll 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.
Geographic signal
Observed country distribution
ThreatInfo has seen TabProtect_Scheduler.dll across 6 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Iran, Islamic Republic of with 30.0% 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 TabProtect_Scheduler.dll is Windows 10 with 83.3% 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
TabProtect_Scheduler.dll is identified as pe for 32-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
7e86b62255a66832d909de92ffa7121c
8e922bed3dfb174361396c5e8298e72b
7f195018475eacf0584da689c7a51d3f
00000000000000000000000000000000
ad6cacf9cb41d79aeba656a53b6709f5
c6612f5881fe814557f842afb8ff4ac7
01c0ccc61fda6b700e845440c5a70b08
db5c25175dfaa343a760a5c0a7afeec2
351ad75c6a0624c7dd8f6b15af3fd4c1
daa711e1947146011dff6d884ac7110b
216c10ab8026647b7fc07b3900441c46
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 file is still under review
ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.