GridinSoft Threat Intelligence

bass_wv.dll file report

Under review File reputation report
MD5 3e73cf8d80e00e4eb832052beef78b2a
Latest seen 2022-11-14 23:36:49 (3 years ago)
First seen 2017-05-21 04:03:44 (8 years ago)
Size 27 KB
Publisher MaresWEB
Product BASS_WV

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 04:03:44 (8 years ago); latest analysis 2022-11-14 23:36:49 (3 years ago).

Publisher context

Company metadata: MaresWEB. Product metadata: BASS_WV.

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.

bass_wv.dll is a Windows file recorded in the ThreatInfo database. It is associated with BASS_WV. The reported company name is MaresWEB. The current detection status is Undefined, based on the latest analysis from 2022-11-14 23:36:49 (3 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: BASS_WV
Company Name: MaresWEB
MD5: 3e73cf8d80e00e4eb832052beef78b2a
Size: 27 KB
First Published: 2017-05-21 04:03:44 (8 years ago)
Latest Published: 2022-11-14 23:36:49 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-11-14 23:36:49 (3 years ago)
%programfiles%\tencent\qqplayer
%programfiles%\baofeng\encoder\codec
%appdata%\pplive\codec\1.0.0.2
%programfiles%\tencent
%programfiles%\tencent\qq player
%programfiles%\qvodplayer
%programfiles%\tc\plugins\wcx
%programfiles%\baofeng\encoder

ThreatInfo has observed bass_wv.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 52.6%
Windows XP 21.1%
Windows 10 16.5%
Windows 8.1 8.1%
Windows 8 1.5%
Windows Vista 0.2%
Windows Server 2012 R2 0.1%

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

bass_wv.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 0x00010036
Image base 0x10000000

PE Sections:

Sections 4
Raw data 27576

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

25600 bytes · 92.8% of section data
Uncommon name
MD5 0e9cefcffc55ea6e3f74e8c39b593eed
.rsrc 952 bytes · 3.5% of section data
MD5 0167504412efb032efe12f235e3ade24
0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
1024 bytes · 3.7% of section data
Uncommon name
MD5 f0b7e2cd56bf532488add5aca9096319

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 3e73cf8d80e00e4eb832052beef78b2a.
  • 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.