MalwareTips
Threat LensFile scan report

Is Calendly Set Up (1).vbs safe?

Verdict
Malicious

The VBS script received a malicious sandbox assessment after launching concealed PowerShell, contacting download infrastructure, and exhibiting process-injection and credential-access indicators.

A completed sandbox run found hostile loader behavior, including hidden PowerShell with execution-policy bypass, remote script and ScreenConnect installer retrieval, and offensive techniques T1055 and T1485. Fortinet and TrendMicro also flagged the script among 4 of 75 engines, supporting the runtime findings despite limited family consensus.

Do not run this file

Quarantine and remove the script without executing it, while keeping endpoint protection enabled. If it already ran, isolate the device and investigate PowerShell, ScreenConnect, LSASS access, credentials, and all observed network destinations.

Read the full analysis
Saved file evidenceAntivirus consensus
4of 75 flagged
Flagged 4No detection 71
Digital specimenCalendly Set Up (1).vbs27d6275671f259d39f…4f496b3bfebb99
Size6.7 KB
Code signingNot applicable
SandboxRuntime complete
First seenToday
Evidence3 priority signals
1 isolated runtime environment classified the observed behavior as malicious.

Recommended next actions

01

Before running

Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.

02

If you already ran it

Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.

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.

94%Confidence
Very high
Analyst conclusion

A completed sandbox run found hostile loader behavior, including hidden PowerShell with execution-policy bypass, remote script and ScreenConnect installer retrieval, and offensive techniques T1055 and T1485. Fortinet and TrendMicro also flagged the script among 4 of 75 engines, supporting the runtime findings despite limited family consensus.

Where this verdict could be wrong4 caveats
  • Only 4/75 engines detected the file, and engines.tier1FamilyConsensus.strong=false; the MALD2 family attribution is therefore not strongly corroborated.
  • contactedHosts.inspected=3 found zero cached malicious or suspicious hosts, although the runtime contact list includes more distinct domains and IP addresses than were inspected.
  • droppedChildren.hasMaliciousChild=false, but the single inspected child remained unclassified rather than receiving a benign result.
  • externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false, providing no researcher-rule or repository corroboration.

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 and remove the script without executing it, while keeping endpoint protection enabled. If it already ran, isolate the device and investigate PowerShell, ScreenConnect, LSASS access, credentials, and all observed network destinations.

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

    4 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    3 of 9 contacted hosts were cross-checked; coverage is incomplete.

  • YARA

    Complete

    5 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
  • 14MITRE ATT&CK techniques
  • 15spawned processes
  • 11network contacts
  • 9filesystem & 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.

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

  • 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: Scans through your files and folders.

  • Note: Reads your Windows user-account details.

  • Note: Collects details about your system.

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 downloaders work

This file is a delivery vehicle. On its own it can look small and harmless, but its job is to quietly pull down and install the REAL payload — often a stealer, ransomware, or bot — from a server the attacker controls.

Bottom line:Because the dangerous part arrives later, early scans can look cleaner than the threat really is.

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 is dangerous. Treat it as harmful and remove it.

  1. Recovery step 01

    Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.

  2. Recovery step 02

    If you already ran 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 developer's official site or an official app store.

Safety FAQ

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

8 evidence-based answers
Is Calendly Set Up (1).vbs a virus?
Evidence-based answer
Yes — Calendly Set Up (1).vbs is malicious. Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash. 4 of 75 antivirus engines flag it (family: MALD2). It behaves as a downloader/dropper whose job is to pull additional malware onto the device. If you've already run it, see the removal and recovery steps below.
What is Calendly Set Up (1).vbs?
Evidence-based answer
Calendly Set Up (1).vbs is a script file, about 7 KB. Our analysis identifies it as malicious (family: MALD2) — a downloader/dropper whose job is to pull additional malware onto the device. 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 Calendly Set Up (1).vbs?
Evidence-based answer
4 of 75 antivirus engines flagged Calendly Set Up (1).vbs, 4 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 is supported by 1 isolated runtime environment that classified the observed behavior as malicious and by the wider saved evidence.
What should I do if I already ran Calendly Set Up (1).vbs?
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 Calendly Set Up (1).vbs?
Evidence-based answer
To remove Calendly Set Up (1).vbs: 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 kind of malware is Calendly Set Up (1).vbs?
Evidence-based answer
Calendly Set Up (1).vbs is classified as a downloader/dropper whose job is to pull additional malware onto the device. Engines attribute it to the MALD2 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 Calendly Set Up (1).vbs?
Evidence-based answer
The SHA-256 hash of Calendly Set Up (1).vbs is 27d6275671f259d39f18a36807500859998ea1a358b063fd084f496b3bfebb99, and its MD5 is 325d61bdda8c3c910c141a62ff3973ea. 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 Calendly Set Up (1).vbs?
Evidence-based answer
This report reflects the scan run on October 6, 2026. Because a file's hash never changes, the identity of Calendly Set Up (1).vbs 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.