Mechanical_Clock_3D_Screensaver.scr threat report

• » File
• File Details
• Overview
• Analysis

Analyst brief

What this report says

GridinSoft Anti-Malware detects Mechanical_Clock_3D_Screensaver.scr as Trojan.Heur!. The sample was last observed on 2022-02-26 23:11:15 (4 years ago) and reports publisher metadata associated with 3Planesoft / Mechanical Clock 3D Screensaver.

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 Trojan.Heur!. 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

Trojan.Heur!

Recommended action

Scan and remove

Last analysis

2022-02-26 23:11:15 (4 years ago)

File hash

6c739aa9139700b0a89bd083f2f1a6c2

Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2022-02-26 23:11:15 (4 years ago); latest analysis 2022-02-26 23:11:15 (4 years ago).

Publisher context

Company metadata: 3Planesoft. Product metadata: Mechanical Clock 3D Screensaver.

Digital signature

Signed by 3Planesoft. 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. 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.

Mechanical_Clock_3D_Screensaver.scr is a Windows file recorded in the ThreatInfo database. It is associated with Mechanical Clock 3D Screensaver. The reported company name is 3Planesoft. The current detection status is Trojan.Heur!, based on the latest analysis from 2022-02-26 23:11:15 (4 years ago).

If Mechanical_Clock_3D_Screensaver.scr 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 Trojan.Heur!.

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 Mechanical_Clock_3D_Screensaver.scr 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 Mechanical_Clock_3D_Screensaver.scr 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.

The strongest geographic signal for this file is Bulgaria with 100.0% 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 Mechanical_Clock_3D_Screensaver.scr is Windows 8.1 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.

Analysis

Mechanical_Clock_3D_Screensaver.scr is identified as pe for 32 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.