GridinSoft Threat Intelligence

00030000000A8BFE.copy file report

Clean record File reputation report
MD5 9de94767760fd8da8cef7c86e2ef3236
Latest seen 2021-02-08 16:51:11 (5 years ago)
First seen 2021-02-08 16:51:11 (5 years ago)
Size 1 MB
Signed by Microsoft Windows

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-02-08 16:51:11 (5 years ago); latest analysis 2021-02-08 16:51:11 (5 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft (R) Windows (R) Operating System.

Digital signature

Signed by Microsoft Windows. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

00030000000A8BFE.copy is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft (R) Windows (R) Operating System. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-02-08 16:51:11 (5 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Microsoft (R) Windows (R) Operating System
Company Name: Microsoft Corporation
MD5: 9de94767760fd8da8cef7c86e2ef3236
Size: 1 MB
First Published: 2021-02-08 16:51:11 (5 years ago)
Latest Published: 2021-02-08 16:51:11 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-08 16:51:11 (5 years ago)
Signed By: Microsoft Windows
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%commonappdata%\bromium\vsentry\4.2.4.52\stage1\stage1image0002\swapdata-c38ff989-d42f-492b-bcd8-f79bb204a254

ThreatInfo has observed 00030000000A8BFE.copy 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 00030000000A8BFE.copy 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.

00030000000A8BFE.copy 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
Image base

.NET Info:

MVID: e882ef2f-e627-43e7-9d0c-e5cae5bea6cd

PE Sections:

Sections 3
Raw data 1306624

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

.data 246784 bytes · 18.9% of section data
MD5 a84c39bf3eb1b4658f89d370e95dea00
.text 990720 bytes · 75.8% of section data
MD5 7065c04bb6bf13533258376ffb87a058
.reloc 69120 bytes · 5.3% of section data
MD5 48a5c6ba7fbe09a4b280a56392a9e473

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 9de94767760fd8da8cef7c86e2ef3236.
  • 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.