Capcom.sys.quarantined threat report

MD5 73c98438ac64a68e88b7b0afd11ba140
Latest seen 2022-04-01 23:16:51 (4 years ago)
First seen 2022-04-01 23:15:00 (4 years ago)
Size 10 KB
Signed by CAPCOM Co.,Ltd.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Risk.CapRoot. 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
Risk.CapRoot
Recommended action
Scan and remove
Last analysis
2022-04-01 23:16:51 (4 years ago)
File hash
73c98438ac64a68e88b7b0afd11ba140
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Risk.CapRoot.

Timeline

First seen 2022-04-01 23:15:00 (4 years ago); latest analysis 2022-04-01 23:16:51 (4 years ago).

Digital signature

Signed by CAPCOM Co.,Ltd.. 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.

Capcom.sys.quarantined is a Windows file recorded in the ThreatInfo database. The current detection status is Risk.CapRoot, based on the latest analysis from 2022-04-01 23:16:51 (4 years ago).

If Capcom.sys.quarantined 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 Risk.CapRoot.

MD5: 73c98438ac64a68e88b7b0afd11ba140
Size: 10 KB
First Published: 2022-04-01 23:15:00 (4 years ago)
Latest Published: 2022-04-01 23:16:51 (4 years ago)
Status: Risk.CapRoot (on last analysis)
Analysis Date: 2022-04-01 23:16:51 (4 years ago)
Capcom.sys.quarantined detection screenshot

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.

Signed By: CAPCOM Co.,Ltd.
Status: Valid

The signature on Capcom.sys.quarantined 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%
%windir%

ThreatInfo has observed Capcom.sys.quarantined 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.

100.0%

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

Windows 10 100.0%

The most common operating system signal for Capcom.sys.quarantined 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.

Capcom.sys.quarantined is identified as pe for 64 systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000000010000
Entry Address: 0x0000063c

PE Sections:

Name Size of data MD5
.text 1280 6b9157859cc28f09e3700def899833b6
.data 256 348a9791dc41b89796ec3808b5b5262f
.pdata 128 12aa0558286840f80503ac72f6db88d9
.info 256 baea8a0197327320ef07208cfa514b40
INIT 384 c1139ed95d2b8e2a7be518b73c486953

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.

More information: