MalwareTips
Threat LensFile scan report

Is Loader[1].rar safe?

Verdict
Malicious

Thirty-one of 75 engines flagged this archive, while tier-1 detections naming Shelma and observed process-injection and defense-impairment techniques indicate a backdoor payload.

The archive drew detections from 31 of 75 engines, including eight high-trust engines. Kaspersky and TrendMicro-HouseCall identify Shelma, while runtime evidence maps activity to process injection and defense impairment; quarantine the archive and do not extract or run it.

Do not open or extract this archive

Quarantine or delete the archive without extracting it, and keep endpoint protection enabled. If it was executed, isolate the system and perform a full security scan and incident review.

Read the full analysis
Saved file evidenceAntivirus consensus
31of 75 flagged
Flagged 31No detection 44
Digital specimenLoader[1].rar6e0b51b82ab691e0a9…9525509a321aa5
Size12.9 MB
Code signingNot applicable
SandboxRuntime complete
First seenToday
Evidence3 priority signals
1 high-confidence signature or behavior rule matched this file.

Recommended next actions

01

Before opening or extracting

Do not open or extract it. Delete this archive from the device, then empty the Recycle Bin or Trash.

02

If you already opened or extracted it

Close it. If it opened links, requested credentials, or triggered unexpected behavior, disconnect from the internet and run a full device scan.

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.

96%Confidence
Very high
Analyst conclusion

The archive drew detections from 31 of 75 engines, including eight high-trust engines. Kaspersky and TrendMicro-HouseCall identify Shelma, while runtime evidence maps activity to process injection and defense impairment; quarantine the archive and do not extract or run it.

Where this verdict could be wrong4 caveats
  • engines.tier1FamilyConsensus.strong=false because only 2 tier-1 engines agree specifically on Shelma.
  • behaviour.hasMaliciousSandboxVerdict=false, although the completed run recorded T1055 and T1562.001.
  • externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect intelligence-coverage gaps for a newly observed sample.
  • droppedChildren.hasMaliciousChild=false, but the two child verdicts are unknown rather than established benign results.

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

Quarantine or delete the archive without extracting it, and keep endpoint protection enabled. If it was executed, isolate the system and perform a full security scan and incident review.

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

    31 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded

  • YARA

    Complete

    1 signature or behavior rule 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
  • 11MITRE ATT&CK techniques
  • 1spawned processes
  • 0network contacts
  • 1filesystem & mutex artifacts

What this file does

Observed actions and their security significance

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

  • High concern: Attempted to impair or bypass security controls.

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

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

  • Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.

  • Moderate concern: Checks which security software you have installed.

  • Note: Reads your Windows user-account details.

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.

Threat context

How remote-access malware works

This opens a secret 'back door' into your computer. Once it's running, an attacker can control your PC from anywhere — see your screen, read your files, switch on your webcam, install more malware, or use your machine to attack others.

Bottom line:It's built to stay hidden and keep that connection open for as long as possible.

Recorded behavior

Attack story

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

ObservedDerived

4 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

This file is dangerous. Treat it as harmful and remove it.

  1. Recovery step 01

    Don't open or extract this archive. Delete this archive from the device, then empty the Recycle Bin or Trash.

  2. Recovery step 02

    If you already opened or extracted it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.

  3. Recovery step 03

    If you typed any passwords while it was open, change them from a device you trust.

  4. Recovery step 04

    Get a fresh copy from the original trusted source and verify its exact hash when possible.

Safety FAQ

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

8 evidence-based answers
Is Loader[1].rar a virus?
Evidence-based answer
Yes — Loader[1].rar is malicious. Do not open or extract it. Delete this archive from the device, then empty the Recycle Bin or Trash. 31 of 75 antivirus engines flag it (family: Shelma). It behaves as a backdoor/remote-access trojan that lets an attacker control the device remotely. If you've already opened or extracted it, see the removal and recovery steps below.
What is Loader[1].rar?
Evidence-based answer
Loader[1].rar is a compressed archive (application/x-compressed), about 12.9 MB. Our analysis identifies it as malicious (family: Shelma) — a backdoor/remote-access trojan that lets an attacker control the device remotely. Because a file's name and icon can be faked, the safest way to identify it is by its cryptographic hash (below), not its filename.
How many antivirus engines detected Loader[1].rar?
Evidence-based answer
31 of 75 antivirus engines flagged Loader[1].rar, 31 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence. The malicious verdict comes from the complete saved evidence, not from this antivirus count by itself.
What should I do if I already opened or extracted Loader[1].rar?
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 Loader[1].rar?
Evidence-based answer
To remove Loader[1].rar: 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 archive 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 kind of malware is Loader[1].rar?
Evidence-based answer
Loader[1].rar is classified as a backdoor/remote-access trojan that lets an attacker control the device remotely. Engines attribute it to the Shelma family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
What is the SHA-256 hash of Loader[1].rar?
Evidence-based answer
The SHA-256 hash of Loader[1].rar is 6e0b51b82ab691e0a96d14303093f6f36dc74ef7c435de7de69525509a321aa5, and its MD5 is e8479731e5e0f4ad598732a34b6736d4. 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 Loader[1].rar?
Evidence-based answer
This report reflects the scan run on September 23, 2026. Because a file's hash never changes, the identity of Loader[1].rar 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.