MalwareTips
Threat LensFile scan report

Is cshred112.exe safe?

Verdict
Suspicious

No antivirus engine detected this long-established file, but one sandbox recorded LSASS access and process-injection mappings that warrant caution before execution.

All 76 antivirus engines were silent, including 15 tier-1 engines, and no curated malware-intelligence match was found. However, the unsigned program produced one sandbox trace involving LSASS targeting, possible process injection, and direct-IP traffic without a completed host-reputation check, so execution should be deferred pending source verification.

Do not run it until verified

Avoid executing this copy until its hash and origin are independently verified. Keep security protection enabled and use an isolated test system if further examination is necessary.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 76 flagged
Flagged 0No detection 76
Digital specimencshred112.exe316e66b4580b7f65e4…1d965dd6398a2e
Size474.5 KB
Code signingUnsigned
SandboxRuntime complete
First seen18y ago
Evidence3 priority signals
1 high-confidence signature or behavior rule matched this file.

Recommended next actions

01

Before running

Do not run it until the source and publisher can be verified independently.

02

If you already ran it

Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

75%Confidence
High
Analyst conclusion

All 76 antivirus engines were silent, including 15 tier-1 engines, and no curated malware-intelligence match was found. However, the unsigned program produced one sandbox trace involving LSASS targeting, possible process injection, and direct-IP traffic without a completed host-reputation check, so execution should be deferred pending source verification.

Where this verdict could be wrong4 caveats
  • The executable is unsigned under signing.signed=false, leaving no publisher identity or signer history to support trust.
  • MalwareTips.Synth.ProcessInjection maps saved runtime activity to T1055, while MalwareTips.Synth.CredentialDumper reports LSASS targeting.
  • behaviour.contactedIps includes 217.20.54.37 and 23.216.81.152, but contactedHosts=null means no complete host-reputation result is available.
  • All 10 entries under droppedChildren.children have verdict=null, so hasMaliciousChild=false does not establish that the dropped files are benign.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Avoid executing this copy until its hash and origin are independently verified. Keep security protection enabled and use an isolated test system if further examination is necessary.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    0 of 76 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    3 runtime contacts were observed without a completed reputation cross-check.

  • YARA

    Complete

    3 signature or behavior rules matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 28MITRE ATT&CK techniques
  • 15spawned processes
  • 3network contacts
  • 40filesystem & mutex artifacts

What this file does

Observed actions and their security significance

  • High concern: Accessed operating-system credential data, which can expose saved passwords.

  • High concern: Injected code into another process, a technique that can conceal execution.

  • High concern: Used an input-capture technique that can record credentials or keystrokes.

  • High concern: Changed an auto-start location that can make code run after sign-in or restart.

  • High concern: Manipulated how the operating system loads code, which can redirect execution.

  • Moderate concern: Contained obfuscated or packed code that makes inspection harder.

  • Moderate concern: Runs hidden system commands (script or shell).

These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & FAQ

Complete recovery guidance and answers for the next decision.

What to do now

We couldn't fully clear this file. Treat it with caution.

  1. Recovery step 01

    Don't run it unless you're certain it came from a source you trust.

  2. Recovery step 02

    Check where you got it — an unexpected attachment or a random download link is a red flag.

  3. Recovery step 03

    If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.

  4. Recovery step 04

    If you're still unsure, scan it again in a day or two — detections often catch up on newer files.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

7 evidence-based answers
Is cshred112.exe safe, or is it malware?
Evidence-based answer
cshred112.exe is suspicious — treat it as unsafe until you're sure. No antivirus engine flagged it; the cautious verdict comes from other saved evidence such as identity, prevalence, signing, or runtime signals. Don't run it unless you fully trust where it came from. Get a fresh copy from the developer's official site or an official app store.
What is cshred112.exe?
Evidence-based answer
cshred112.exe is a Windows executable program, about 475 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
How many antivirus engines detected cshred112.exe?
Evidence-based answer
None — 0 of 76 antivirus engines flagged cshred112.exe. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
What should I do if I already ran cshred112.exe?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove cshred112.exe?
Evidence-based answer
To remove cshred112.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What is the SHA-256 hash of cshred112.exe?
Evidence-based answer
The SHA-256 hash of cshred112.exe is 316e66b4580b7f65e48856bfd629b4eb61eb5588bc8b3049621d965dd6398a2e, and its MD5 is 90d1e6f6600422a37ce97c2e399e048b. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of cshred112.exe?
Evidence-based answer
This report reflects the scan run on September 22, 2026. Because a file's hash never changes, the identity of cshred112.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Scan another
Check a different file
URL instead?
Check if a link is safe
The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.