GridinSoft Threat Intelligence

FastestChrome_p1v2.exe file report

Under review File reputation report
MD5 07b9c6d3e061fa80c7fc4809a75ea223
Latest seen 2025-02-17 23:00:51 (a year ago)
First seen 2017-08-20 17:14:16 (8 years ago)
Size 592 KB
Signed by OpenCandy Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-08-20 17:14:16 (8 years ago); latest analysis 2025-02-17 23:00:51 (a year ago).

Digital signature

Signed by OpenCandy 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.

FastestChrome_p1v2.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-02-17 23:00:51 (a year 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: 07b9c6d3e061fa80c7fc4809a75ea223
Size: 592 KB
First Published: 2017-08-20 17:14:16 (8 years ago)
Latest Published: 2025-02-17 23:00:51 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-17 23:00:51 (a year ago)
Signed By: OpenCandy Inc.
Status: Valid

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

%appdata%\opencandy\a3c30154a7d943ce833c82cc418055bf
%appdata%\opencandy

ThreatInfo has observed FastestChrome_p1v2.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 7 50.0%
Windows 10 50.0%

The most common operating system signal for FastestChrome_p1v2.exe is Windows 7 with 50.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.

FastestChrome_p1v2.exe 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 0x00003883
Image base 0x00400000

PE Sections:

Sections 6
Raw data 46592

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

.text 28160 bytes · 60.4% of section data
MD5 00499a6f70259150109c809d6aa0e6ed
.rdata 11264 bytes · 24.2% of section data
MD5 07990aaa54c3bc638bb87a87f3fb13e3
.data 512 bytes · 1.1% of section data
MD5 014871d9a00f0e0c8c2a7cd25606c453
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.rsrc 2560 bytes · 5.5% of section data
MD5 ba21f03a123fdfef9e0085fffbba4cc7
.reloc 4096 bytes · 8.8% of section data
MD5 92fa8fcae391cb5932b1e3b72628cc2e

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 07b9c6d3e061fa80c7fc4809a75ea223.
  • 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.