File scan report

Verdict Malicious

Analyzed , 3 months ago

Is &Bill of Lading (BL).vbs safe? No, we rate this exact file malicious.

Five major antivirus engines flag the script as a downloader with labels including ISB.Downloader!gen40 and HEUR:Trojan-Downloader.Script.Generic.

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Don't run this file

If you already ran it, follow the steps below.

What to do now4 steps

This file is harmful. Don't run it, and remove it.

If you haven't run it

  1. Don't run this file. Delete it, then empty the Recycle Bin.

If you already ran it

  1. Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.

  2. If you typed passwords on the device after running it, change them from another device you trust.

  3. If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.

If you already ran it, do these in order.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

Paste this report's link in your topic so helpers can see what was found.

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

9 of 61 flagged

  • Flagged 9
  • No detection 52
  • No result 13
File&Bill of Lading (BL).vbs4.6 kBSHA-256 37ffa3580a83…613b36
  • Code signing Not applicable
  • Test run Completed
  • First seen 3mo ago
9 of the 61 antivirus engines that checked it flag it, including Kaspersky and Avast.

Chapter 02

Why we think so

4 points against it and 3 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The combination of offensive MITRE techniques and major detections outweighs the lack of external-intel hits.

Where this verdict could be wrong3 caveats
  • No community YARA rule matched and MalwareBazaar.hit=false — no researcher-curated rules or known family match on this exact hash.
  • droppedChildren.hasMaliciousChild=false and contactedHosts.maliciousHosts.length=0 — no confirmed malicious files it created or previously-seen malicious hosts in our cache.
  • engines.reporting=61 out of 74 total but only 9 malicious; 52 undetected engines leave room for possible over-flagging on an obfuscated script.

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

6 sources checked · 5 complete · 1 partial. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 38sandbox rule tags
  • 7spawned processes
  • 8network contacts
  • 33filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Created a scheduled task so it runs again later.

  • Moderate concern: Created a Windows service so it keeps running.

  • Moderate concern: Set itself to start automatically after a restart.

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.

  • Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

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 fetch and install the real payload, often a password stealer, ransomware or a 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

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      &Bill of Lading (BL).vbs

      37ffa3580a83f170525c7b422faf529b72968e870c0124b1fbac95a4cc613b36

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      MsiExec.exe

      C:\Windows\syswow64\MsiExec.exe -Embedding A6F7ECBA80BE918C9BF05E4078066861

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      dcagentregister.exe

      "C:\Program Files (x86)\ManageEngine\UEMS_Agent\bin\dcagentregister.exe" -i dc

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      dcagentinstaller.log

      C:\Program Files (x86)\ManageEngine\UEMS_Agent\logs\dcagentinstaller.log

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      csr.pem

      C:\Program Files (x86)\ManageEngine\UEMS_Agent\Certificates\csr.pem

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      38.207.189.45

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      23.195.81.162

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

9 of the 61 antivirus engines that checked it flag it.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 74 enginesCompleteRisk signal: 9 of 61 engines flagged it · 13 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial4 of 8 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteWorth noting: 2 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 9

  • Avast (major engine)Script:SNH-gen [Drp]
  • AVG (major engine)Script:SNH-gen [Drp]
  • Avira (major engine)DR/SNH
  • F-Secure (major engine)Dropper.DR/SNH
  • Kaspersky (major engine)HEUR:Trojan-Downloader.Script.Generic
  • Symantec (major engine)ISB.Downloader!gen40
  • CynetMalicious (score: 99)
  • NANO-AntivirusTrojan.Script.Vbs-heuristic.druvzi
1 more in the full engine list

File fingerprint

Last analyzed
Jul 13, 2026, 8:12 AM UTC
SHA-256
37ffa3580a83f170525c7b422faf529b72968e870c0124b1fbac95a4cc613b36
SHA-1
959a61f8f09d7ba49983998d87174e2289e2b30d
MD5
8e08eeeed20479429602e10f0816bbc1

About this file

&Bill of Lading (BL).vbs is a VBA file of 4.6 kB.

Type and size
VBA · 4.6 kB
Signer
Not applicable
First seen
Jul 13, 2026On VirusTotal.
Submitted by
1 sourceRarely seen: few people have submitted this exact file.

First scanned

Chapter 05

Questions & answers

Short answers to the 8 questions people ask most about this file.

Is &Bill of Lading (BL).vbs malware?
Yes. This copy of &Bill of Lading (BL).vbs (SHA-256 37ffa358…3b36) is malicious. Other files with the same name can be different, so check the hash. Don't run it. Delete it, then empty the Recycle Bin. 9 of the 61 antivirus engines that checked it flag it, some as druvzi. Antivirus engines classify it as a downloader whose job is to fetch more malware onto the device. If you've already run it, see the steps below.
What is &Bill of Lading (BL).vbs?
&Bill of Lading (BL).vbs is a VBScript file, about 4.6 kB. VirusTotal first saw it on Jul 13, 2026.
How many antivirus engines detected &Bill of Lading (BL).vbs?
9 of the 61 antivirus engines that checked it flag &Bill of Lading (BL).vbs, including Kaspersky and Avast. We weigh which engines flagged it and what else the scan found, not just the count. The rating comes from all the evidence together, not from this count alone.
I already downloaded and ran &Bill of Lading (BL).vbs — what should I do?
Act quickly. 1) Disconnect the device from the internet. 2) Run a full scan with your antivirus and let it remove what it finds. 3) Change your important passwords from another device you trust, starting with email and banking, and turn on two-step verification. 4) If you bank or shop on this device, watch your accounts and tell your bank about payments you don't recognise. 5) If the scan keeps finding it, back up your personal files and reinstall Windows.
How do I remove &Bill of Lading (BL).vbs?
To remove &Bill of Lading (BL).vbs: 1) run a full scan with your antivirus and let it remove what it finds. 2) Delete it, then empty the Recycle Bin. 3) Check Settings > Apps, your browser extensions, startup apps (Task Manager > Startup apps) and scheduled tasks for anything you don't recognise. 4) Restart and scan again. If it keeps coming back, scan from Safe Mode with Networking, or back up your files and reinstall Windows.
What kind of malware is &Bill of Lading (BL).vbs?
Antivirus engines classify &Bill of Lading (BL).vbs as a downloader whose job is to fetch more malware onto the device. Engines attribute it to the druvzi family.
What is the SHA-256 hash of &Bill of Lading (BL).vbs?
The SHA-256 fingerprint of &Bill of Lading (BL).vbs is 37ffa3580a83f170525c7b422faf529b72968e870c0124b1fbac95a4cc613b36, and its MD5 is 8e08eeeed20479429602e10f0816bbc1. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of &Bill of Lading (BL).vbs?
This report reflects the scan on Jul 13, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.