GridinSoft Threat Intelligence

bx_digital V2.dll file report

Under review File reputation report
MD5 075b3b264e1313be5cfc0f09474c18bd
Latest seen 2024-05-12 23:00:36 (2 years ago)
First seen 2024-05-06 23:00:36 (2 years ago)
Size 4 MB
Publisher Plugin Alliance
Product bx_digital V2

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-05-06 23:00:36 (2 years ago); latest analysis 2024-05-12 23:00:36 (2 years ago).

Publisher context

Company metadata: Plugin Alliance. Product metadata: bx_digital V2.

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.

bx_digital V2.dll is a Windows file recorded in the ThreatInfo database. It is associated with bx_digital V2. The reported company name is Plugin Alliance. The current detection status is Undefined, based on the latest analysis from 2024-05-12 23:00:36 (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.

Product Name: bx_digital V2
Company Name: Plugin Alliance
MD5: 075b3b264e1313be5cfc0f09474c18bd
Size: 4 MB
First Published: 2024-05-06 23:00:36 (2 years ago)
Latest Published: 2024-05-12 23:00:36 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-12 23:00:36 (2 years ago)
%commondir%

ThreatInfo has observed bx_digital V2.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 10 100.0%

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

bx_digital V2.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00028da8
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 4766208

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

.text 587776 bytes · 12.3% of section data
MD5 7b7739db670ec620be65adc7a0721de4
.rdata 612864 bytes · 12.9% of section data
MD5 516c2858e3c055020ef23a9a42ec32d7
.data 471040 bytes · 9.9% of section data
MD5 561a2ef9cd7da48833580a9d484f19eb
.pdata 30720 bytes · 0.6% of section data
MD5 d26175be283a9511f71fbb5d1d78f61c
.shared 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 3038720 bytes · 63.8% of section data
MD5 33c4bfd709bb0ae7d13f54038c096019
.reloc 24576 bytes · 0.5% of section data
MD5 b9b8225a63b4c63c011bbdb74570dd03

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 075b3b264e1313be5cfc0f09474c18bd.
  • 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.