GridinSoft Threat Intelligence

pubmod.dll file report

Under review File reputation report
MD5 de1803ffcde354c9fb9b8f1bfeb09e4a
Latest seen 2025-02-06 23:05:57 (a year ago)
First seen 2017-08-11 01:00:53 (8 years ago)
Size 60 KB
Publisher Yahoo! Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-08-11 01:00:53 (8 years ago); latest analysis 2025-02-06 23:05:57 (a year ago).

Publisher context

Company metadata: Yahoo! Inc.. Product metadata: PopupBlocker Module for Yahoo! Companion.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

pubmod.dll is a Windows file recorded in the ThreatInfo database. It is associated with PopupBlocker Module for Yahoo! Companion. The reported company name is Yahoo! Inc.. The current detection status is Undefined, based on the latest analysis from 2025-02-06 23:05:57 (a year 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.

Product Name: PopupBlocker Module for Yahoo! Companion
Company Name: Yahoo! Inc.
MD5: de1803ffcde354c9fb9b8f1bfeb09e4a
Size: 60 KB
First Published: 2017-08-11 01:00:53 (8 years ago)
Latest Published: 2025-02-06 23:05:57 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-06 23:05:57 (a year ago)
%programfiles%\yahoo!\companion\installs\cpn
%programfiles%\yahoo!\companion\installs

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

Windows XP 47.9%
Windows 7 28.1%
Windows 10 16.7%
Windows 8.1 3.1%
Windows 8 3.1%
Windows Vista 1.0%

The most common operating system signal for pubmod.dll is Windows XP with 47.9% 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.

pubmod.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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0000ad65
Image base 0x65200000

PE Sections:

Sections 5
Raw data 60416

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

.text 40960 bytes · 67.8% of section data
MD5 11d1b25497ff75a58b1fa80f89fb8787
.rdata 8704 bytes · 14.4% of section data
MD5 98946528a9d33b26d35d0c1a05ec9bc9
.data 512 bytes · 0.8% of section data
MD5 47bf17c7d7acef4b450972e6ca8267c8
.rsrc 5632 bytes · 9.3% of section data
MD5 5100a81fe6030e39cf4995d854e4c331
.reloc 4608 bytes · 7.6% of section data
MD5 4910cf9dabba525cd769a67f104f3ca2

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.

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