GridinSoft Threat Intelligence

pub.exe file report

Clean record File reputation report
MD5 6b226b9cc285efe432fa68e30bd0a75a
Latest seen 2023-05-06 23:20:01 (3 years ago)
First seen 2023-05-06 23:20:01 (3 years ago)
Size 4 MB
Publisher ESTsoft Corp.
Product ALPopskin

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-05-06 23:20:01 (3 years ago); latest analysis 2023-05-06 23:20:01 (3 years ago).

Publisher context

Company metadata: ESTsoft Corp.. Product metadata: ALPopskin.

Digital signature

Signed by Hewlett-Packard Company. 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.

pub.exe is a Windows file recorded in the ThreatInfo database. It is associated with ALPopskin. The reported company name is ESTsoft Corp.. The current detection status is Clean, based on the latest analysis from 2023-05-06 23:20:01 (3 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: ALPopskin
Company Name: ESTsoft Corp.
MD5: 6b226b9cc285efe432fa68e30bd0a75a
Size: 4 MB
First Published: 2023-05-06 23:20:01 (3 years ago)
Latest Published: 2023-05-06 23:20:01 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-05-06 23:20:01 (3 years ago)
Signed By: Hewlett-Packard Company
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.

%programfiles%

ThreatInfo has observed pub.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 10 100.0%

The most common operating system signal for pub.exe 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.

pub.exe 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 0x0061d188
Image base 0x0000000000400000

PE Sections:

Sections 6
Raw data 4207104

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

727552 bytes · 17.3% of section data
Uncommon name
MD5 4b5340b6948b1aa6ebd0db604ce26fd0
17408 bytes · 0.4% of section data
Uncommon name
MD5 aac7ab9a32f6231138152db3c1419b36
.idata 512 bytes · 0.0% of section data
MD5 2133a125c5cdd4fb213e0a3cc7727e31
.rsrc 97280 bytes · 2.3% of section data
MD5 269c53740ee55ba1ea4a44fefabbaa3a
.themida 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 3364352 bytes · 80.0% of section data
Uncommon name
MD5 ce9726da279da6c36aa50ac5b8edf7f7

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 6b226b9cc285efe432fa68e30bd0a75a.
  • 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.