MD5 f08c3f6a98d5929edf8e1f7e5d45d75f
Latest seen 2021-03-26 21:43:10 (5 years ago)
First seen 2021-03-26 21:43:10 (5 years ago)
Size 58 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:43:10 (5 years ago); latest analysis 2021-03-26 21:43:10 (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.

magD11F.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:43:10 (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: f08c3f6a98d5929edf8e1f7e5d45d75f
Size: 58 MB
First Published: 2021-03-26 21:43:10 (5 years ago)
Latest Published: 2021-03-26 21:43:10 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-26 21:43:10 (5 years ago)
Signed By: LLC Mail.Ru
Status: Valid

The signature on magD11F.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 magD11F.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 magD11F.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.

magD11F.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 0x0002791f
Image base 0x00400000

PE Sections:

Sections 5
Raw data 61733376

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

.text 292352 bytes · 0.5% of section data
MD5 1973c903674653b8fdbd199756921f1b
.rdata 90112 bytes · 0.1% of section data
MD5 036484bb1f205b9819597190f380a9e9
.data 6656 bytes · 0.0% of section data
MD5 8592e978e8d3dc64a1c6f5cca7d6fab1
.rsrc 61329408 bytes · 99.3% of section data
Large raw data
MD5 2c25431a134bc14d0c44657b388a98af
.reloc 14848 bytes · 0.0% of section data
MD5 7197bd479f064b0ef3ad66d355d0ecef

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