GridinSoft Threat Intelligence

2BF1.exe file report

Clean record File reputation report
MD5 a6d56826b34c3aa9a52354ced8b3b209
Latest seen 2021-01-14 13:39:33 (5 years ago)
First seen 2021-01-14 13:39:33 (5 years ago)
Size 3 MB
Product xOBlqimvKl818
Signed by Kaspersky Lab

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-14 13:39:33 (5 years ago); latest analysis 2021-01-14 13:39:33 (5 years ago).

Publisher context

Company metadata: PqyJjhagfoA UnogBTpuDGrQirt AnAvBoIRev eiUvyZ. Product metadata: xOBlqimvKl818.

Digital signature

Signed by Kaspersky Lab. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

2BF1.exe is a Windows file recorded in the ThreatInfo database. It is associated with xOBlqimvKl818. The reported company name is PqyJjhagfoA UnogBTpuDGrQirt AnAvBoIRev eiUvyZ. The current detection status is Clean, based on the latest analysis from 2021-01-14 13:39:33 (5 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: xOBlqimvKl818
Company Name: PqyJjhagfoA UnogBTpuDGrQirt AnAvBoIRev eiUvyZ
MD5: a6d56826b34c3aa9a52354ced8b3b209
Size: 3 MB
First Published: 2021-01-14 13:39:33 (5 years ago)
Latest Published: 2021-01-14 13:39:33 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-14 13:39:33 (5 years ago)
Signed By: Kaspersky Lab
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%temp%

ThreatInfo has observed 2BF1.exe 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 7 100.0%

The most common operating system signal for 2BF1.exe is Windows 7 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.

2BF1.exe 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 0x00573058
Image base 0x00400000

PE Sections:

Sections 11
Raw data 3485173

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

295410 bytes · 8.5% of section data
Uncommon name
MD5 439a42e2244d2bc2fc92419d4b8dd025
48552 bytes · 1.4% of section data
Uncommon name
MD5 79a1d1721d842b59929f0ecb3d037967
1163 bytes · 0.0% of section data
Uncommon name
MD5 c89f97c24a65ac397c9261c85b8b827b
19547 bytes · 0.6% of section data
Uncommon name
MD5 56bc635f14feed75cbcb7db76c2b586c
17253 bytes · 0.5% of section data
Uncommon name
MD5 32f4df7e2d4c263998ef5047a3b126dc
.imports 512 bytes · 0.0% of section data
Uncommon name
MD5 72273857eaa08b157818e285ba8717eb
.tls 512 bytes · 0.0% of section data
MD5 9008521fe5a7ac4bd06ac21800061756
.rsrc 29184 bytes · 0.8% of section data
MD5 3aaca4be76f8f3ff14fa16bae38de884
.themida 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 3073024 bytes · 88.2% of section data
Uncommon name
MD5 db7493d1375eeb05c6a3d079e55f1cba
.reloc 16 bytes · 0.0% of section data
MD5 70aa363d5d8dfa40c34f51f89e32d05a

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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