MD5 6186a38dc5d86a5a193da24affb6c41b
Latest seen 2021-03-26 21:54:05 (5 years ago)
First seen 2021-03-26 21:54:05 (5 years ago)
Size 59 MB
Signed by LLC Mail.Ru

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-03-26 21:54:05 (5 years ago); latest analysis 2021-03-26 21:54:05 (5 years ago).

Publisher context

Product metadata: Mail.ru Agent Setup.

Digital signature

Signed by LLC Mail.Ru. The signature is reported as valid, but signed files can still be bundled or abused.

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.

magF527.tmp is a Windows file recorded in the ThreatInfo database. It is associated with Mail.ru Agent Setup. The current detection status is Undefined, based on the latest analysis from 2021-03-26 21:54:05 (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: Mail.ru Agent Setup
MD5: 6186a38dc5d86a5a193da24affb6c41b
Size: 59 MB
First Published: 2021-03-26 21:54:05 (5 years ago)
Latest Published: 2021-03-26 21:54:05 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-26 21:54:05 (5 years ago)
Signed By: LLC Mail.Ru
Status: Valid

The signature on magF527.tmp is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%temp%

ThreatInfo has observed magF527.tmp 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 100.0%

The most common operating system signal for magF527.tmp is Windows 10 with 100.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.

magF527.tmp 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 0x000279f6
Image base 0x00400000

PE Sections:

Sections 5
Raw data 61982720

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

.text 292864 bytes · 0.5% of section data
MD5 2a473e6a8de7d98c12b0e9870c370f64
.rdata 90624 bytes · 0.1% of section data
MD5 63e6763a2ce56369d48a606dbfcf5ce3
.data 6656 bytes · 0.0% of section data
MD5 c69b04d763408cfa8f8b22cb6f124833
.rsrc 61577728 bytes · 99.3% of section data
Large raw data
MD5 580374e19652fc6dc737637917e89770
.reloc 14848 bytes · 0.0% of section data
MD5 c16ce718df4a77fedc401a3baf811b97

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 6186a38dc5d86a5a193da24affb6c41b.
  • 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.