GridinSoft Threat Intelligence

WcCommunication.exe file report

Under review File reputation report
MD5 b2fa0edd860ab48fdcb6ece2449e0518
Latest seen 2021-07-01 20:20:46 (4 years ago)
First seen 2020-05-18 05:40:50 (6 years ago)
Size 28 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-05-18 05:40:50 (6 years ago); latest analysis 2021-07-01 20:20:46 (4 years ago).

Publisher context

Product metadata: WebCompanion.Communication.

Digital signature

Signed by LAVASOFT SOFTWARE CANADA 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.

WcCommunication.exe is a Windows file recorded in the ThreatInfo database. It is associated with WebCompanion.Communication. The current detection status is Undefined, based on the latest analysis from 2021-07-01 20:20:46 (4 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.

Product Name: WebCompanion.Communication
MD5: b2fa0edd860ab48fdcb6ece2449e0518
Size: 28 KB
First Published: 2020-05-18 05:40:50 (6 years ago)
Latest Published: 2021-07-01 20:20:46 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-07-01 20:20:46 (4 years ago)
Signed By: LAVASOFT SOFTWARE CANADA INC
Status: Valid

The signature on WcCommunication.exe 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.

%programfiles%\lavasoft\web companion

ThreatInfo has observed WcCommunication.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 66.7%
Windows 7 22.2%
Windows 8.1 11.1%

The most common operating system signal for WcCommunication.exe is Windows 10 with 66.7% 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.

WcCommunication.exe 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 0x00004f8e
Image base 0x00400000

.NET Info:

MVID: 8ca03bcc-b2c5-4161-8248-72383d3866ca
Typelib ID: 744f51ef-ed39-4b7c-b99b-d5d1e3a2ebba

PE Sections:

Sections 3
Raw data 14336

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

.text 12288 bytes · 85.7% of section data
MD5 f5d7af607724d38b28da191e6ec298cb
.rsrc 1536 bytes · 10.7% of section data
MD5 5cac106370ea02e678edcd09e3fb0da2
.reloc 512 bytes · 3.6% of section data
MD5 1e993afff2cae841f4e27fae0a03c9a0

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