GridinSoft Threat Intelligence

BabylonRPI.api file report

Under review File reputation report
MD5 0f07cd44ba2bfbea1dfd6a73af2bb746
Latest seen 2021-01-14 15:17:06 (5 years ago)
First seen 2017-05-22 09:01:45 (9 years ago)
Size 64 KB
Publisher Babylon

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 09:01:45 (9 years ago); latest analysis 2021-01-14 15:17:06 (5 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 2021-01-14 15:17:06 (5 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: 0f07cd44ba2bfbea1dfd6a73af2bb746
Size: 64 KB
First Published: 2017-05-22 09:01:45 (9 years ago)
Latest Published: 2021-01-14 15:17:06 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-14 15:17:06 (5 years ago)
%sysdrive%\programmi\babylon\utils
%programfiles%\babylon\babylon-pro\utils
%programfiles%\babylon\utils
%sysdrive%\programmi\babylon
%programfiles%\babylon\babylon-pro
%programfiles%\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 7 41.5%
Windows 10 34.0%
Windows 8.1 13.2%
Windows 8 7.5%
Windows XP 3.8%

The most common operating system signal for BabylonRPI.api is Windows 7 with 41.5% 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 0x00004bf9
Image base 0x10000000

PE Sections:

Sections 5
Raw data 61440

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

.text 40960 bytes · 66.7% of section data
MD5 fcc3e18e1e5c5dcaa16ecdd11c994e75
.rdata 8192 bytes · 13.3% of section data
MD5 949bec6f40f0ebc07722c3077903e2db
.data 4096 bytes · 6.7% of section data
MD5 268354d4d868b4207fc9560c5f73582f
.rsrc 4096 bytes · 6.7% of section data
MD5 de3b865106fd2fa1fdd9ab131eb054a4
.reloc 4096 bytes · 6.7% of section data
MD5 87891f37a1fff95a083d0fbe17db9535

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 0f07cd44ba2bfbea1dfd6a73af2bb746.
  • 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.