GridinSoft Threat Intelligence

bx_dynEQ V2 Mono.dll file report

Under review File reputation report
MD5 6fa762adde8f0965d60c376dae8977b4
Latest seen 2024-05-12 23:00:37 (2 years ago)
First seen 2024-05-06 23:00:33 (2 years ago)
Size 4 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:33 (2 years ago); latest analysis 2024-05-12 23:00:37 (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 Mono.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:37 (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: 6fa762adde8f0965d60c376dae8977b4
Size: 4 MB
First Published: 2024-05-06 23:00:33 (2 years ago)
Latest Published: 2024-05-12 23:00:37 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-12 23:00:37 (2 years ago)
%commondir%

ThreatInfo has observed bx_dynEQ V2 Mono.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 Mono.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 Mono.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 4950528

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

.text 521216 bytes · 10.5% of section data
MD5 a6138e1bcd19ace7aaf85ffb9b9507f1
.rdata 578048 bytes · 11.7% of section data
MD5 b419bc9f7bffc9826dcfd49321fa6a09
.data 471552 bytes · 9.5% of section data
MD5 e39a12646bb6870fe1f8c3c2f87690f9
.pdata 29696 bytes · 0.6% of section data
MD5 ec5f53db2688fcce8a8d870d2d7ca938
.shared 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 3323904 bytes · 67.1% of section data
MD5 a806a2416645461f64eff06a6ccc715c
.reloc 25600 bytes · 0.5% of section data
MD5 656c43fdc2ab505ef22411314fc95882

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 6fa762adde8f0965d60c376dae8977b4.
  • 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.