procid64.dll.bak threat report

• » File
• File Details
• Overview
• Analysis

Analyst brief

What this report says

GridinSoft Anti-Malware detects procid64.dll.bak as PUP.Gen. The sample was last observed on 2023-01-02 23:54:53 (3 years ago).

This page combines the detection verdict with file identity, publisher metadata, alternate names, observed paths, geography, OS signals, and PE details so the report reads as a triage record rather than a standalone download page.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.Gen. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name

PUP.Gen

Recommended action

Scan and remove

Last analysis

2023-01-02 23:54:53 (3 years ago)

File hash

0e593e581d5e8245a79b9c24a29ce87d

Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.Gen.

Timeline

First seen 2017-08-24 21:08:01 (8 years ago); latest analysis 2023-01-02 23:54:53 (3 years ago).

Digital signature

Signed by Destiny Media. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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. Compare the MD5 above with the file found on the device.
2. Check whether the file appears in the observed locations or under one of the alternate names.
3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

procid64.dll.bak is a Windows file recorded in the ThreatInfo database. The current detection status is PUP.Gen, based on the latest analysis from 2023-01-02 23:54:53 (3 years ago).

If procid64.dll.bak appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as PUP.Gen.

File Details

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Overview

The signature on procid64.dll.bak 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.

ThreatInfo has observed procid64.dll.bak 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.

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

The strongest geographic signal for this file is Ukraine with 72.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

The most common operating system signal for procid64.dll.bak is Windows 7 with 95.5% 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.

Analysis

procid64.dll.bak is identified as pe for 64 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.

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.