GridinSoft Threat Intelligence

control.exb file report

Under review File reputation report
MD5 f1f2f926d98a166be8fc38a9e428d00c
Latest seen 2025-09-04 23:01:21 (8 months ago)
First seen 2017-09-15 07:12:23 (8 years ago)
Size 115 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-15 07:12:23 (8 years ago); latest analysis 2025-09-04 23:01:21 (8 months ago).

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.

control.exb is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-09-04 23:01:21 (8 months 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.

MD5: f1f2f926d98a166be8fc38a9e428d00c
Size: 115 KB
First Published: 2017-09-15 07:12:23 (8 years ago)
Latest Published: 2025-09-04 23:01:21 (8 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-09-04 23:01:21 (8 months ago)
%sysdrive%\zv\noexp\files
%commonappdata%\net protector\nposfile\2017-07-14_2036\files
%commonappdata%\net protector\nposfile\2017-05-28_1205\files
%commonappdata%\net protector\nposfile\2017-09-16_1148\files
%commonappdata%\net protector\nposfile\2017-09-15_1142\files
%commonappdata%\net protector\nposfile\2020-07-19_1019
%commonappdata%\net protector\nposfile\2018-02-20_1157
%commonappdata%\net protector\nposfile\2018-01-19_1220
%commonappdata%\net protector\nposfile\2017-12-17_1057
%system%

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

control.exb is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x000012e0
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 116736

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

.text 6144 bytes · 5.3% of section data
MD5 b07d5ff81369848c932175c0690e7f5c
.rdata 7680 bytes · 6.6% of section data
MD5 5b0fc5fcd323b6beb9e90d3cfc62e017
.data 512 bytes · 0.4% of section data
MD5 faaef9cd90101840434e88223aaa01c4
.pdata 1024 bytes · 0.9% of section data
MD5 73c19bd5bc85c6362625e4028ede5cab
.rsrc 100864 bytes · 86.4% of section data
MD5 675a28693a29ef1ecb875d9216769a9d
.reloc 512 bytes · 0.4% of section data
MD5 5c1aed3185a542152f35626756a8ce11

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