MD5 c0c4eca64a913e80e823a05aefb2a1c9
Latest seen 2021-11-08 21:34:37 (4 years ago)
First seen 2021-11-08 21:32:08 (4 years ago)
Size 2 MB
Publisher
Product BitComet

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-11-08 21:32:08 (4 years ago); latest analysis 2021-11-08 21:34:37 (4 years ago).

Publisher context

Company metadata: . Product metadata: BitComet .

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.

File context

Bit88C4.tmp.tmp is a Windows file recorded in the ThreatInfo database. It is associated with BitComet . The reported company name is . The current detection status is Undefined, based on the latest analysis from 2021-11-08 21:34:37 (4 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.

File Details

Product Name: BitComet
Company Name:
MD5: c0c4eca64a913e80e823a05aefb2a1c9
Size: 2 MB
First Published: 2021-11-08 21:32:08 (4 years ago)
Latest Published: 2021-11-08 21:34:37 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-08 21:34:37 (4 years ago)

Geographic signal

Observed country distribution

ThreatInfo has seen Bit88C4.tmp.tmp across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Brazil
Share 100.0%
Low High activity

The strongest geographic signal for this file is Brazil with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 100.0%

The most common operating system signal for Bit88C4.tmp.tmp 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.

Analysis

Bit88C4.tmp.tmp 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 0x002c3650
Image base 0x00400000

PE Sections:

Sections 10
Raw data 3036160

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

.text 2882048 bytes · 94.9% of section data
MD5 89ce14e009257957f5e2941ac2286230
.itext 10752 bytes · 0.4% of section data
Uncommon name
MD5 a8ea4b7956e1b51171165830d3ce6a78
.data 37376 bytes · 1.2% of section data
MD5 586ad30a8215d7030e5320e27bce3ca4
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 14848 bytes · 0.5% of section data
MD5 9a10d495545bbe0d0c173e5160012f77
.didata 3072 bytes · 0.1% of section data
Uncommon name
MD5 2937589ef8b41cb66bf6ca8aa8fcd7af
.edata 512 bytes · 0.0% of section data
MD5 1fa460bfb714a17109f4d1b931b695e1
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.0% of section data
MD5 ab111d8950af4c4fa175bda002954fdb
.rsrc 87040 bytes · 2.9% of section data
MD5 549d0b4c62523b0795f49aa6282dcd6f

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 c0c4eca64a913e80e823a05aefb2a1c9.
  • 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.