GridinSoft Threat Intelligence

Tmp18C6.tmp file report

Under review File reputation report
MD5 5b13e5448adeb430c5d33f67a853081a
Latest seen 2021-01-10 16:53:56 (5 years ago)
First seen 2020-10-30 09:05:58 (5 years ago)
Size 141 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-30 09:05:58 (5 years ago); latest analysis 2021-01-10 16:53:56 (5 years ago).

Publisher context

Product metadata: Segurazo Antivirus.

Digital signature

Signed by Digital Communications Inc.. 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.

Tmp18C6.tmp is a Windows file recorded in the ThreatInfo database. It is associated with Segurazo Antivirus. The current detection status is Undefined, based on the latest analysis from 2021-01-10 16:53:56 (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: Segurazo Antivirus
MD5: 5b13e5448adeb430c5d33f67a853081a
Size: 141 KB
First Published: 2020-10-30 09:05:58 (5 years ago)
Latest Published: 2021-01-10 16:53:56 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-10 16:53:56 (5 years ago)
Signed By: Digital Communications Inc.
Status: Valid

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

%windir%
%commonappdata%\segurazo

ThreatInfo has observed Tmp18C6.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 7 100.0%

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

Tmp18C6.tmp 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 0x0002009e
Image base 0x00400000

.NET Info:

MVID: df7fdac3-3bf6-4e6e-bf7a-9d5160b69e56
Typelib ID: 583a09ef-cbe7-4b3f-a9dc-d7cc60acabf9

PE Sections:

Sections 4
Raw data 126464

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

.text 123392 bytes · 97.6% of section data
MD5 5d051d65e86727f3c323e69b33a0f82c
.sdata 1024 bytes · 0.8% of section data
Uncommon name
MD5 88eff384d74cfcd413a3e0c80a295eee
.rsrc 1536 bytes · 1.2% of section data
MD5 6d65e54b3ded7e4e78d275a1a775516f
.reloc 512 bytes · 0.4% of section data
MD5 bc27aa2e7b0edcdb68a450862c50fcb7

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 5b13e5448adeb430c5d33f67a853081a.
  • 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.