File scan report
Verdict Malicious
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.
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
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
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.
If you typed passwords on the device after running it, change them from another device you trust.
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.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
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
- Code signing Not applicable
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The combination of offensive MITRE techniques and major detections outweighs the lack of external-intel hits.
The file is a 4.6 KB obfuscated VBA script submitted for the first time today. Five major antivirus engines plus Kaspersky label it a generic downloader or dropper. Sandbox execution revealed eight offensive MITRE techniques, direct contact with six raw IPs, and attempts to create persistence via ManageEngine services. No code signing, no prior similar-hash matches, and a rare and prevalence classification further support malicious intent. While external YARA and file it created checks returned clean, the major consensus and concrete behavioural red flags dominate the evidence.
What We Detected
Five major antivirus engines (Avast, AVG, Avira, F-Secure, Symantec) and Kaspersky returned malicious verdicts on the VBA script. Labels reference generic dropper and downloader families (SNH-gen, ISB.Downloader!gen40). The script carries tags for obfuscation, anti-analysis, and download activity.
Threat Behavior
Several URLs point to bgedea.cc for payload retrieval. No DNS resolution was observed, a common malware evasion tactic.
What To Do Now
Quarantine or delete the file immediately. Block the observed IPs and domains at the network perimeter. Scan the host for additional dropped files and persistence mechanisms. Review any ManageEngine UEMS processes that may have been abused for persistence.
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.
- No malicious files it created detected
- No prior similar-hash matches in our database
- No YARAify or CIRCL external-intel hits
- Major antivirus engine consensus on downloader activity
- Direct-IP a control server bypassing DNS reputation systems
- Persistence indicators for ManageEngine services
- Rare_new file with no signing or prior reputation
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.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
&Bill of Lading (BL).vbs
37ffa3580a83f170525c7b422faf529b72968e870c0124b1fbac95a4cc613b36
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
MsiExec.exe
C:\Windows\syswow64\MsiExec.exe -Embedding A6F7ECBA80BE918C9BF05E4078066861
Test run - 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 - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
dcagentinstaller.log
C:\Program Files (x86)\ManageEngine\UEMS_Agent\logs\dcagentinstaller.log
Test run - Evidence 5 of 7: Written fileSeen in the test run
csr.pem
C:\Program Files (x86)\ManageEngine\UEMS_Agent\Certificates\csr.pem
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
38.207.189.45
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.195.81.162
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 38 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 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.
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
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
Includes every engine result (74), 2 matched signature rules and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is &Bill of Lading (BL).vbs malware?
What is &Bill of Lading (BL).vbs?
How many antivirus engines detected &Bill of Lading (BL).vbs?
I already downloaded and ran &Bill of Lading (BL).vbs — what should I do?
How do I remove &Bill of Lading (BL).vbs?
What kind of malware is &Bill of Lading (BL).vbs?
What is the SHA-256 hash of &Bill of Lading (BL).vbs?
How up to date is this analysis of &Bill of Lading (BL).vbs?
Community
Member reviews and reports for this exact file hash.