GridinSoft Threat Intelligence

mcvidrv.sys file report

Under review File reputation report
MD5 df6560dc4f437b28e7bb9eb2d5b1230e
Latest seen 2021-11-16 21:13:55 (4 years ago)
First seen 2019-03-31 04:25:35 (7 years ago)
Size 39 KB
Publisher Visicom Media Inc.
Product ManyCam Virtual Webcam
Signed by Visicom Media Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2019-03-31 04:25:35 (7 years ago); latest analysis 2021-11-16 21:13:55 (4 years ago).

Publisher context

Company metadata: Visicom Media Inc.. Product metadata: ManyCam Virtual Webcam.

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

mcvidrv.sys is a Windows file recorded in the ThreatInfo database. It is associated with ManyCam Virtual Webcam. The reported company name is Visicom Media Inc.. The current detection status is Undefined, based on the latest analysis from 2021-11-16 21:13:55 (4 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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: ManyCam Virtual Webcam
Company Name: Visicom Media Inc.
MD5: df6560dc4f437b28e7bb9eb2d5b1230e
Size: 39 KB
First Published: 2019-03-31 04:25:35 (7 years ago)
Latest Published: 2021-11-16 21:13:55 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-16 21:13:55 (4 years ago)

Overview

Signed By: Visicom Media Inc.
Status: Valid

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

%system%
%system%\driverstore\filerepository

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

Top country Indonesia
Share 40.0%
Low High activity

The strongest geographic signal for this file is Indonesia with 40.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 90.9%
Windows Embedded Standard 9.1%

The most common operating system signal for mcvidrv.sys is Windows 7 with 90.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.

Analysis

mcvidrv.sys is identified as pe for 32-bit systems. The subsystem is Native. 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 Native
Entry point 0x0000783e
Image base 0x00010000

PE Sections:

Sections 7
Raw data 32512

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

.text 16640 bytes · 51.2% of section data
MD5 c5c123cbc19ac2f8d916900fbbbf1998
.rdata 1408 bytes · 4.3% of section data
MD5 8018adf53bb6de07b52376fac5211a6e
.data 11136 bytes · 34.3% of section data
MD5 b6455507baaee2eb4b8624acef3c164e
PAGECONS 384 bytes · 1.2% of section data
Uncommon name
MD5 42aa37b4c5a537e6c00f8eecd96163bb
INIT 1152 bytes · 3.5% of section data
Uncommon name
MD5 aba02910be28dca0466486b3e214ccd6
.rsrc 896 bytes · 2.8% of section data
MD5 32bbc46fbe45f4abe28b4ab91665bf52
.reloc 896 bytes · 2.8% of section data
MD5 2252600c4eafb14e630336a770040c47

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 df6560dc4f437b28e7bb9eb2d5b1230e.
  • 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. Use the PUP category to compare similar reports.