GridinSoft Threat Intelligence

BCC BumpMap.aex file report

Under review File reputation report
MD5 8268924ff013048424d8936017915758
Latest seen 2023-02-28 23:25:17 (3 years ago)
First seen 2023-02-28 23:25:17 (3 years ago)
Size 2 MB
Publisher Boris FX, Inc.
Product Boris FX(tm)

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-02-28 23:25:17 (3 years ago); latest analysis 2023-02-28 23:25:17 (3 years ago).

Publisher context

Company metadata: Boris FX, Inc.. Product metadata: Boris FX(tm).

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.

BCC BumpMap.aex is a Windows file recorded in the ThreatInfo database. It is associated with Boris FX(tm). The reported company name is Boris FX, Inc.. The current detection status is Undefined, based on the latest analysis from 2023-02-28 23:25:17 (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: Boris FX(tm)
Company Name: Boris FX, Inc.
MD5: 8268924ff013048424d8936017915758
Size: 2 MB
First Published: 2023-02-28 23:25:17 (3 years ago)
Latest Published: 2023-02-28 23:25:17 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-02-28 23:25:17 (3 years ago)
%programfiles%\boris fx, inc

ThreatInfo has observed BCC BumpMap.aex 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 BCC BumpMap.aex 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.

BCC BumpMap.aex 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 0x0003bf50
Image base 0x00400000

PE Sections:

Sections 10
Raw data 2993152

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

.text 366080 bytes · 12.2% of section data
MD5 632056ac9ce9a2d5d7ada4b57fad5aa5
.rdata 27648 bytes · 0.9% of section data
MD5 6a6c084d5889f2d17adaf3ee3aa1d29b
.exc 12288 bytes · 0.4% of section data
Uncommon name
MD5 0e5f64702f1a71b01f50dceecf45c6db
.rsrc 115712 bytes · 3.9% of section data
MD5 02c248f96bdfed598902862b0d10b074
.data 2433536 bytes · 81.3% of section data
MD5 e00d0c60febd33908d00a8e1ca3306c4
.CRT 512 bytes · 0.0% of section data
MD5 527427a73bc5ac4a3c4111035afb05af
.idata 3584 bytes · 0.1% of section data
MD5 fd23733758996aec0cd110b462a7a4cf
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.edata 512 bytes · 0.0% of section data
MD5 9280cc142b2141139f1626c742973e4d
.reloc 33280 bytes · 1.1% of section data
MD5 6ef9e5a685383f4efdf7e26ff7c69fac

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 8268924ff013048424d8936017915758.
  • 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.