Threat LensFile scan report

Is config safe?

Verdict
Safe

Safe file assessment

0 of 74 antivirus engines flagged the file.

Open with normal care

Open with normal care

Read the full analysis
Saved file evidenceAntivirus consensus
0of 74 flagged
Flagged 0No detection 74
Digital specimenconfig60099cf91bb1a5717f…bae98c560bf3d5
Size3.2 KB
Code signingNot applicable
SandboxRuntime complete
First seen7y ago
Evidence3 priority signals
0 of 74 antivirus engines flagged the file.

Recommended next actions

01

Before opening

Open it only when its sender or download source is one you independently trust.

02

If you already opened it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

Chapter 02

Intelligence

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

No saved analyst narrative

This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.

Scan transparency

Coverage & freshness

5 of 5 complete

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

  • Antivirus

    Complete

    0 of 74 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Complete

    3 contacted hosts were cross-checked.

  • YARA

    Complete

    2 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
  • 22MITRE ATT&CK techniques
  • 15spawned processes
  • 4network contacts
  • 30filesystem & mutex artifacts
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

This file appears low risk based on the evidence available now.

  1. Recovery step 01

    Open it only when its sender or download source is one you independently trust.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

  3. Recovery step 03

    Keep your antivirus and Windows updates switched on so you stay protected.

Safety FAQ

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

6 evidence-based answers
Is config safe?
Evidence-based answer
config appears safe. 0 of 74 antivirus engines flagged it. Open it only when its sender or download source is one you independently trust.
What is config?
Evidence-based answer
config is a file, about 3 KB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected config?
Evidence-based answer
None — 0 of 74 antivirus engines flagged config. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
What is the SHA-256 hash of config?
Evidence-based answer
The SHA-256 hash of config is 60099cf91bb1a5717fc1f2d23cf36a61d3bfb70d9489fbb6f4bae98c560bf3d5, and its MD5 is d9bc824737177af5792846f26507231c. 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.
Is it safe to open config?
Evidence-based answer
Based on the recorded evidence, config has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
How up to date is this analysis of config?
Evidence-based answer
This report reflects the scan run on July 4, 2026. Because a file's hash never changes, the identity of config 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.

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.