MD5 9905f43e175c7db1508296a3b1771308
Latest seen 2021-06-14 20:17:10 (4 years ago)
First seen 2021-06-14 20:17:10 (4 years ago)
Size 39 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:17:10 (4 years ago); latest analysis 2021-06-14 20:17:10 (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.

magCF1F.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:17:10 (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: 9905f43e175c7db1508296a3b1771308
Size: 39 MB
First Published: 2021-06-14 20:17:10 (4 years ago)
Latest Published: 2021-06-14 20:17:10 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-14 20:17:10 (4 years ago)
Signed By: LLC Mail.Ru
Status: Valid

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

magCF1F.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 0x0001eeba
Image base 0x00400000

PE Sections:

Sections 5
Raw data 41095168

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

.text 250368 bytes · 0.6% of section data
MD5 6166c1912452d41c6973d8beebdb0199
.rdata 77312 bytes · 0.2% of section data
MD5 2ae1a700d8e04b71d38ce097c6eaff23
.data 6656 bytes · 0.0% of section data
MD5 0f13d6ecf9ed5f272600c85207c2f207
.rsrc 40747008 bytes · 99.2% of section data
Large raw data
MD5 4e6342c5ae6750857ec9770f8ed147df
.reloc 13824 bytes · 0.0% of section data
MD5 7afb48299944dd67d238863d69f109fa

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 9905f43e175c7db1508296a3b1771308.
  • 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.