ThreatInfo has not assigned a final verdict to RDLMA.exe. The metadata below can still help compare the file identity, origin, and observed behavior against a copy found on a device.
This page combines the detection verdict with file identity, publisher metadata, alternate names, observed paths, geography, OS signals, and PE details so the report reads as a triage record rather than a standalone download page.
Why it matters
Evidence available for this file
Detection
No final classification is available yet.
Timeline
First seen 2017-08-12 03:08:09 (8 years ago); latest analysis 2021-04-05 20:27:04 (5 years ago).
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
Use the hash and metadata below to verify the exact file identity.
Review publisher, signature, paths, and PE details for inconsistencies.
Run a local scan if the file appears unexpectedly or starts with Windows.
File context
RDLMA.exe is a Windows file recorded in the ThreatInfo database.
It is associated with Windows Installer - Unicode.
The reported company name is Microsoft Corporation.
The current detection status is Undefined, based on the latest analysis from 2021-04-05 20:27:04 (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.
ThreatInfo has observed RDLMA.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.
This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geographic signal
Observed country distribution
ThreatInfo has seen RDLMA.exe across 52 countries. Use this signal to compare local evidence with where the sample is most often reported.
Top countryRussian Federation
Share24.1%
LowHigh activity
The strongest geographic signal for this file is Russian Federation with 24.1% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
Windows 8.196.0%
Windows 104.0%
The most common operating system signal for RDLMA.exe is Windows 8.1 with 96.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.
Analysis
PE Info:
RDLMA.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.
Formatpe
Architecture32-bit
SubsystemWindows GUI
Entry point0x0000187a
Image base0x00400000
PE Sections:
Sections5
Raw data54784
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
.text34304 bytes · 62.6% of section data
MD51b85baadfa4f5ec9b0116b11547220ba
.data6144 bytes · 11.2% of section data
MD5fd31e90b08cc9f6de0d5c3f116b2d61b
.idata3584 bytes · 6.5% of section data
MD58bd52171a4917286e8403adefac9e81c
.rsrc8192 bytes · 15.0% of section data
MD58578f6c0f122878f84c966a38d3a0d79
.reloc2560 bytes · 4.7% of section data
MD584a0d7552b5714967c761fb9ff7f15a4
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.