GridinSoft Threat Intelligence

sysbbanalyzer.exe file report

Clean record File reputation report
MD5 7d1c6f3b4291745006b0f318107a3111
Latest seen 2021-01-04 05:02:13 (5 years ago)
First seen 2018-11-06 00:07:10 (7 years ago)
Size 1 MB
Publisher Webroot
Signed by Webroot Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-11-06 00:07:10 (7 years ago); latest analysis 2021-01-04 05:02:13 (5 years ago).

Publisher context

Company metadata: Webroot. Product metadata: Webroot SecureAnywhere.

Digital signature

Signed by Webroot Inc.. ThreatInfo marks this publisher as trusted for this record.

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.

sysbbanalyzer.exe is a Windows file recorded in the ThreatInfo database. It is associated with Webroot SecureAnywhere. The reported company name is Webroot. The current detection status is Clean, based on the latest analysis from 2021-01-04 05:02:13 (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.

Product Name: Webroot SecureAnywhere
Company Name: Webroot
MD5: 7d1c6f3b4291745006b0f318107a3111
Size: 1 MB
First Published: 2018-11-06 00:07:10 (7 years ago)
Latest Published: 2021-01-04 05:02:13 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-04 05:02:13 (5 years ago)
Signed By: Webroot Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%profile%

ThreatInfo has observed sysbbanalyzer.exe 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 8 50.0%
Windows 10 50.0%

The most common operating system signal for sysbbanalyzer.exe is Windows 8 with 50.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.

sysbbanalyzer.exe 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00391320
Image base 0x01000000

PE Sections:

Sections 3
Raw data 1222656

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

UPX0 0 bytes · 0.0% of section data
Packer marker Uncommon name
MD5 00000000000000000000000000000000
UPX1 1200128 bytes · 98.2% of section data
Packer marker Uncommon name
MD5 209c4947d28cf8371a3d33cfc21bd029
.rsrc 22528 bytes · 1.8% of section data
MD5 58a38ef81a9d43e218bd92ba007fecdc

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 7d1c6f3b4291745006b0f318107a3111.
  • 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.