GridinSoft Threat Intelligence

BabylonRPI.api file report

Under review File reputation report
MD5 b2c38f5bd371aa21650420e1dd2a54d4
Latest seen 2024-01-15 23:04:08 (2 years ago)
First seen 2017-09-26 03:07:12 (8 years ago)
Size 157 KB
Publisher Babylon

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-26 03:07:12 (8 years ago); latest analysis 2024-01-15 23:04:08 (2 years ago).

Publisher context

Company metadata: Babylon. Product metadata: Babylon BabylonRPI.

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.

BabylonRPI.api is a Windows file recorded in the ThreatInfo database. It is associated with Babylon BabylonRPI. The reported company name is Babylon. The current detection status is Undefined, based on the latest analysis from 2024-01-15 23:04:08 (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 BabylonRPI
Company Name: Babylon
MD5: b2c38f5bd371aa21650420e1dd2a54d4
Size: 157 KB
First Published: 2017-09-26 03:07:12 (8 years ago)
Latest Published: 2024-01-15 23:04:08 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-15 23:04:08 (2 years ago)
%programfiles%\babylon\babylon-pro\utils
%profile%\ser\local settings\application data\babylon
%programfiles%\babylon\babylon-pro
%localappdata%\babylon

ThreatInfo has observed BabylonRPI.api 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 BabylonRPI.api 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.

BabylonRPI.api 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 0x0000ac8e
Image base 0x10000000

PE Sections:

Sections 5
Raw data 160256

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

.text 118272 bytes · 73.8% of section data
MD5 d25e0bf58ef1b65db68c8baf0f99199d
.rdata 23552 bytes · 14.7% of section data
MD5 db220d2d7085242162add01c27fce82b
.data 6144 bytes · 3.8% of section data
MD5 41b60a26ecc2af2660afe6d48f9601fe
.rsrc 3072 bytes · 1.9% of section data
MD5 c8c54d04a700af57b9b16dc4aa9b5a34
.reloc 9216 bytes · 5.8% of section data
MD5 f3ad0528657606d62f4fc6fb1a40212d

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