GridinSoft Threat Intelligence

BCC Film Damage.aex file report

Under review File reputation report
MD5 96a68bb566f9409f6264d4708cca2927
Latest seen 2023-02-28 23:24:30 (3 years ago)
First seen 2023-02-28 23:24:30 (3 years ago)
Size 740 KB
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:24:30 (3 years ago); latest analysis 2023-02-28 23:24:30 (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 Film Damage.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:24:30 (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: 96a68bb566f9409f6264d4708cca2927
Size: 740 KB
First Published: 2023-02-28 23:24:30 (3 years ago)
Latest Published: 2023-02-28 23:24:30 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-02-28 23:24:30 (3 years ago)
%programfiles%\boris fx, inc

ThreatInfo has observed BCC Film Damage.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 Film Damage.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 Film Damage.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 0x0004a130
Image base 0x00400000

PE Sections:

Sections 10
Raw data 756736

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

.text 409600 bytes · 54.1% of section data
MD5 fa859cf4e42a3ce2469333fc5d8b5376
.rdata 31744 bytes · 4.2% of section data
MD5 0aac785d5e0428d9676425697ec223a4
.exc 14336 bytes · 1.9% of section data
Uncommon name
MD5 24d9e4794286d329f80feb466e8f0f50
.rsrc 115712 bytes · 15.3% of section data
MD5 bd076afd7f7fb5199a75990fe67ff7c4
.data 142336 bytes · 18.8% of section data
MD5 65a81c35b328f2452277f2d80d05f6e4
.CRT 512 bytes · 0.1% of section data
MD5 7489760a497d1eb2302c775b8dad73c5
.idata 3584 bytes · 0.5% of section data
MD5 c8b052ef76d8228e001b059073943186
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.edata 512 bytes · 0.1% of section data
MD5 0e68f420d112a75c6bd51364758761d9
.reloc 38400 bytes · 5.1% of section data
MD5 55eec1554280f316616bca695f182cc3

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 96a68bb566f9409f6264d4708cca2927.
  • 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.