GridinSoft Threat Intelligence

011913.EXE file report

Under review File reputation report
MD5 e46aefcdeba94119d70c00c564da1984
Latest seen 2021-03-05 04:34:30 (5 years ago)
First seen 2017-06-08 07:10:20 (8 years ago)
Size 26 MB
Product MEncoder

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-08 07:10:20 (8 years ago); latest analysis 2021-03-05 04:34:30 (5 years ago).

Publisher context

Product metadata: MEncoder.

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.

011913.EXE is a Windows file recorded in the ThreatInfo database. It is associated with MEncoder. The current detection status is Undefined, based on the latest analysis from 2021-03-05 04:34:30 (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: MEncoder
MD5: e46aefcdeba94119d70c00c564da1984
Size: 26 MB
First Published: 2017-06-08 07:10:20 (8 years ago)
Latest Published: 2021-03-05 04:34:30 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-05 04:34:30 (5 years ago)
%sysdrive%\zv\outbox
%programfiles%\formatfactory\ffmodules

ThreatInfo has observed 011913.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.

Windows 10 78.6%
Windows 7 21.4%

The most common operating system signal for 011913.EXE is Windows 10 with 78.6% 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.

011913.EXE is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x000014e0
Image base 0x00400000

PE Sections:

Sections 10
Raw data 27412992

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

.text 19998208 bytes · 73.0% of section data
Large raw data
MD5 90e66570ed0e27a4aa2ddfd5ef5e6cdc
.rotext 112128 bytes · 0.4% of section data
Uncommon name
MD5 d30afa108772885277d743ee60dd0151
.data 207872 bytes · 0.8% of section data
MD5 6e1eb5b03a4c6daeb42d684b718b02fc
.rdata 6915072 bytes · 25.2% of section data
Large raw data
MD5 60eeeae72fd7523bdb28c4c79c84d1e4
.rodata 55296 bytes · 0.2% of section data
MD5 de1b679a7e56b61963d54219f7cf2dce
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 10752 bytes · 0.0% of section data
MD5 816b6326ce212793a312f5c48cbb8ab4
.CRT 512 bytes · 0.0% of section data
MD5 53d5af67e7f564b5b52eb672878507d0
.tls 512 bytes · 0.0% of section data
MD5 312d8428e13092215dd446fcaea85ba0
.rsrc 112640 bytes · 0.4% of section data
MD5 2fedac17c29fc90a49ea81cc9b4a2a04

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