GridinSoft Threat Intelligence

viscomavi.dll file report

Under review File reputation report
MD5 b2808319f304b768c02dd3e537daceaf
Latest seen 2021-01-04 20:13:08 (5 years ago)
First seen 2021-01-04 20:13:08 (5 years ago)
Size 17 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-04 20:13:08 (5 years ago); latest analysis 2021-01-04 20:13:08 (5 years ago).

Publisher context

Company metadata: Viscom Software www.viscomsoft.com.

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.

viscomavi.dll is a Windows file recorded in the ThreatInfo database. The reported company name is Viscom Software www.viscomsoft.com. The current detection status is Undefined, based on the latest analysis from 2021-01-04 20:13:08 (5 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.

Company Name: Viscom Software www.viscomsoft.com
MD5: b2808319f304b768c02dd3e537daceaf
Size: 17 MB
First Published: 2021-01-04 20:13:08 (5 years ago)
Latest Published: 2021-01-04 20:13:08 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-04 20:13:08 (5 years ago)
%programfiles%\aml products

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

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

viscomavi.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 0x0029c63b
Image base 0x10000000

PE Sections:

Sections 9
Raw data 18624512

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

.text 3883008 bytes · 20.8% of section data
MD5 33f91c2fde9ad392aa4a1a22eae98954
.rodata 12288 bytes · 0.1% of section data
MD5 ee1ee1ceaa2f1789d7790f9bd4f596e2
.rdata 729088 bytes · 3.9% of section data
MD5 62f01a33c1945208b717ed781e382a4a
.data 122880 bytes · 0.7% of section data
MD5 18a9dd73d5cfea0d0baa883480cf30fd
.dtors 4096 bytes · 0.0% of section data
Uncommon name
MD5 5908f10a593bc99c29444448c7c18a88
.stab 6070272 bytes · 32.6% of section data
Large raw data Uncommon name
MD5 914418ee2e000d672c26bfd56ba9baff
.stabstr 7614464 bytes · 40.9% of section data
Large raw data Uncommon name
MD5 2156f6896030dfe55711f32f8bd37233
.rsrc 4096 bytes · 0.0% of section data
MD5 0236aa05df845ce91241e7b5d9d37942
.reloc 184320 bytes · 1.0% of section data
MD5 da4e7e65326584a654d90de1845fc53a

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