GridinSoft Threat Intelligence

MyStart_antiphishing.dll file report

Under review File reputation report
MD5 ef7493c08308cd5283e4b7a59ff7cb0b
Latest seen 2024-04-23 23:00:52 (2 years ago)
First seen 2024-04-23 23:00:52 (2 years ago)
Size 311 KB
Publisher Visicom Media Inc.
Product MyStart Anti-phishing Domain Advisor (Powered by Panda Security)
Signed by Visicom Media Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-04-23 23:00:52 (2 years ago); latest analysis 2024-04-23 23:00:52 (2 years ago).

Publisher context

Company metadata: Visicom Media Inc.. Product metadata: MyStart Anti-phishing Domain Advisor (Powered by Panda Security).

Digital signature

Signed by Visicom Media Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

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.

File context

MyStart_antiphishing.dll is a Windows file recorded in the ThreatInfo database. It is associated with MyStart Anti-phishing Domain Advisor (Powered by Panda Security). The reported company name is Visicom Media Inc.. The current detection status is Undefined, based on the latest analysis from 2024-04-23 23:00:52 (2 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: MyStart Anti-phishing Domain Advisor (Powered by Panda Security)
Company Name: Visicom Media Inc.
MD5: ef7493c08308cd5283e4b7a59ff7cb0b
Size: 311 KB
First Published: 2024-04-23 23:00:52 (2 years ago)
Latest Published: 2024-04-23 23:00:52 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-04-23 23:00:52 (2 years ago)

Overview

Signed By: Visicom Media Inc.
Status: Valid

The signature on MyStart_antiphishing.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:

%commonappdata%

ThreatInfo has observed MyStart_antiphishing.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 MyStart_antiphishing.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Egypt
Share 100.0%
Low High activity

The strongest geographic signal for this file is Egypt with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 7 100.0%

The most common operating system signal for MyStart_antiphishing.dll is Windows 7 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.

Analysis

MyStart_antiphishing.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x0002e4df
Image base 0x10000000

PE Sections:

Sections 8
Raw data 311808

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

CODE 124416 bytes · 39.9% of section data
MD5 fc42d1f1681695f9ba2db5b16e25e874
.text 111104 bytes · 35.6% of section data
MD5 558064fa0b70dfbb1100482785700750
.rdata 30208 bytes · 9.7% of section data
MD5 847b1fc65e945890e8709d3a5b9929cd
.data 5120 bytes · 1.6% of section data
MD5 66bf261ced1223a4ea056e251eaf47a7
DATA 5632 bytes · 1.8% of section data
MD5 203093df75f08a8ebd9d4c8dbfe04812
BSS 2560 bytes · 0.8% of section data
MD5 a371492f16c0940507435909603efe88
.rsrc 16384 bytes · 5.3% of section data
MD5 b7190ea9063c24f160799682ba8f6fd9
.reloc 16384 bytes · 5.3% of section data
MD5 fd434067f8a48df9dbd2a663c4e214fe

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