GridinSoft Threat Intelligence

bx_dynEQ V2.dll file report

Under review File reputation report
MD5 8e8421c8ac66492cd9fe8e8c126b7ec7
Latest seen 2024-05-12 23:00:35 (2 years ago)
First seen 2024-05-06 23:00:37 (2 years ago)
Size 12 MB
Publisher Plugin Alliance
Product bx_dynEQ V2

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

Company metadata: Plugin Alliance. Product metadata: bx_dynEQ 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_dynEQ V2.dll is a Windows file recorded in the ThreatInfo database. It is associated with bx_dynEQ 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:35 (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_dynEQ V2
Company Name: Plugin Alliance
MD5: 8e8421c8ac66492cd9fe8e8c126b7ec7
Size: 12 MB
First Published: 2024-05-06 23:00:37 (2 years ago)
Latest Published: 2024-05-12 23:00:35 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-12 23:00:35 (2 years ago)
%commondir%

ThreatInfo has observed bx_dynEQ 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_dynEQ 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_dynEQ 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 0x00029760
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 12775936

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

.text 548352 bytes · 4.3% of section data
MD5 3bbab508e9430965d8c56a77feb40ed4
.rdata 585216 bytes · 4.6% of section data
MD5 5684795a8cc3d64e3d619abcc3d0ad0c
.data 471552 bytes · 3.7% of section data
MD5 69757df5d2e44453cb75179f86b2b0b5
.pdata 30208 bytes · 0.2% of section data
MD5 3503d665ff9c78bb7fb91ee9fc86ed48
.shared 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 11095552 bytes · 86.8% of section data
Large raw data
MD5 c03e7ad700a90f2531d9443fdf6e9177
.reloc 44544 bytes · 0.3% of section data
MD5 eb6b558006740b5721b5c3de9834640b

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 8e8421c8ac66492cd9fe8e8c126b7ec7.
  • 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.