MD5 0be2b7e4b8ef73bdb3d03a71361b7747
Latest seen 2021-06-14 20:25:19 (4 years ago)
First seen 2021-06-14 20:18:32 (4 years ago)
Size 50 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-06-14 20:18:32 (4 years ago); latest analysis 2021-06-14 20:25:19 (4 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.

mag6F3.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-06-14 20:25:19 (4 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: 0be2b7e4b8ef73bdb3d03a71361b7747
Size: 50 MB
First Published: 2021-06-14 20:18:32 (4 years ago)
Latest Published: 2021-06-14 20:25:19 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-14 20:25:19 (4 years ago)
Signed By: LLC Mail.Ru
Status: Valid

The signature on mag6F3.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 mag6F3.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 8 100.0%

The most common operating system signal for mag6F3.tmp is Windows 8 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.

mag6F3.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 0x000263ac
Image base 0x00400000

PE Sections:

Sections 5
Raw data 52907008

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

.text 282112 bytes · 0.5% of section data
MD5 4b775827c09776fe6dab7f2bc88b0f0d
.rdata 92160 bytes · 0.2% of section data
MD5 4814226a2103ae02334a30b71ef9a784
.data 6656 bytes · 0.0% of section data
MD5 b1b016489cef1baeec0c5028784ecb04
.rsrc 52511232 bytes · 99.3% of section data
Large raw data
MD5 a82ef32781e50ca57a60c7e5cbcdf770
.reloc 14848 bytes · 0.0% of section data
MD5 b2ceccd434d82e33b77372814757bf4e

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