GridinSoft Threat Intelligence

captlib64.dll file report

Under review File reputation report
MD5 b3a6fd3375ee91cc88ad4d4936ad76ee
Latest seen 2023-04-27 23:14:42 (3 years ago)
First seen 2017-07-30 14:05:00 (8 years ago)
Size 279 KB
Publisher Babylon Ltd.
Product Babylon Client

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-07-30 14:05:00 (8 years ago); latest analysis 2023-04-27 23:14:42 (3 years ago).

Publisher context

Company metadata: Babylon Ltd.. Product metadata: Babylon Client.

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.

captlib64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Babylon Client. The reported company name is Babylon Ltd.. The current detection status is Undefined, based on the latest analysis from 2023-04-27 23:14:42 (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: Babylon Client
Company Name: Babylon Ltd.
MD5: b3a6fd3375ee91cc88ad4d4936ad76ee
Size: 279 KB
First Published: 2017-07-30 14:05:00 (8 years ago)
Latest Published: 2023-04-27 23:14:42 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-04-27 23:14:42 (3 years ago)
%programfiles%\babylon\babylon-pro
%localappdata%\babylon\setup
%programfiles%\babylon

ThreatInfo has observed captlib64.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 7 60.0%
Windows 10 40.0%

The most common operating system signal for captlib64.dll is Windows 7 with 60.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.

captlib64.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 0x00014be8
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 285184

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

.text 200192 bytes · 70.2% of section data
MD5 2cb56b5bbe66f0b8df4ad8525fdf0a0c
.rdata 50688 bytes · 17.8% of section data
MD5 251f256d5d5f9bede6225ceeee36f721
.data 14336 bytes · 5.0% of section data
MD5 c88cf8711119b779e00fbc64e369eb2c
.pdata 13312 bytes · 4.7% of section data
MD5 56fbf4d3f696bfe9c7eb479644f8b9bc
.SHARDAT 3072 bytes · 1.1% of section data
Uncommon name
MD5 004c1a455953c2162d44c19f3d44db63
.rsrc 1536 bytes · 0.5% of section data
MD5 944435201c4b69a67750f4c7c24ea698
.reloc 2048 bytes · 0.7% of section data
MD5 0b6b0b948f4ee34c05b2cb0deb1f5221

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