GridinSoft Threat Intelligence

captlib.dll file report

Under review File reputation report
MD5 6132b91ab946a77639436c16d3af7236
Latest seen 2024-01-15 23:03:22 (2 years ago)
First seen 2017-09-26 03:07:10 (8 years ago)
Size 224 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-09-26 03:07:10 (8 years ago); latest analysis 2024-01-15 23:03:22 (2 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.

captlib.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 2024-01-15 23:03:22 (2 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: 6132b91ab946a77639436c16d3af7236
Size: 224 KB
First Published: 2017-09-26 03:07:10 (8 years ago)
Latest Published: 2024-01-15 23:03:22 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-15 23:03:22 (2 years ago)
%programfiles%\babylon\babylon-pro
%profile%\ser\local settings\application data\babylon
%programfiles%\babylon
%localappdata%\babylon

ThreatInfo has observed captlib.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 10 36.0%
Windows 7 32.0%
Windows XP 20.0%
Windows 8.1 8.0%
Windows 8 4.0%

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

captlib.dll 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 0x00012a69
Image base 0x10000000

PE Sections:

Sections 6
Raw data 228352

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

.text 169472 bytes · 74.2% of section data
MD5 702f4ed61f273ae0b956cf26713289d9
.rdata 29184 bytes · 12.8% of section data
MD5 1ad15dbc74051840f066144516a96c5c
.data 12800 bytes · 5.6% of section data
MD5 4f741d5030cbf08c11d151f4316103ab
.SHARDAT 3072 bytes · 1.3% of section data
Uncommon name
MD5 24191625e078da4890131cb52278fc13
.rsrc 1536 bytes · 0.7% of section data
MD5 81a5cfafaaf2a4c46398c594cc07c469
.reloc 12288 bytes · 5.4% of section data
MD5 ab46af7f94d856685ef2c7fb096799ce

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 6132b91ab946a77639436c16d3af7236.
  • 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.