Is BBRWSetup.EXE safe?
Eight tier-1 engines flagged this unsigned installer, two identify Egairtigado, and YARA plus runtime injection indicators provide independent corroboration.
The executable drew detections from 24 of 75 engines, including eight tier-1 products. Microsoft and Symantec identify Egairtigado, while Kaspersky reports an Agent dropper; two YARA rules and runtime indicators for process injection and token manipulation reinforce the concern.
996eb82fd67c9fb9f3…7cf0f6c4c7e4f3Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The executable drew detections from 24 of 75 engines, including eight tier-1 products. Microsoft and Symantec identify Egairtigado, while Kaspersky reports an Agent dropper; two YARA rules and runtime indicators for process injection and token manipulation reinforce the concern.
The detection volume is substantial: 24 of 75 engines flagged the executable, including eight tier-1 products. Microsoft and Symantec independently use the Egairtigado family name, although the family consensus does not reach the strong three-engine threshold. Kaspersky, GData, and several other engines identify it as an Agent trojan or dropper. A completed sandbox recorded T1055 and T1134, and two researcher-authored YARA rules matched shellcode and an installer stub. The executable is unsigned and has no established publisher history to counterbalance these signals. No complete contacted-host reputation result is available, and the five dropped children remain unclassified rather than confirmed benign.
What We Detected
Twenty-four of 75 antivirus engines flagged BBRWSetup.EXE, including eight tier-1 products. Microsoft and Symantec identify the Egairtigado family, while Kaspersky reports an Agent dropper and GData reports an Agent trojan. The executable is unsigned and has no verified publisher history.
Threat Behavior
One completed sandbox run mapped activity to T1055, associated with process injection, and T1134, associated with access-token manipulation. Two researcher-authored YARA rules also matched: shellcode and WiseInstallerStub. No sandbox produced an explicit malicious verdict or recorded network contacts, but no complete contacted-host reputation cross-check is available. Five dropped files were inspected, yet all remain unclassified.
What To Do Now
Do not run the executable. Keep endpoint protection enabled, quarantine or remove the file, and perform a full system scan if it was opened; on a managed device, preserve the hash and notify the security team.
Where this verdict could be wrong4 caveats
- engines.tier1FamilyConsensus.strong=false: only Microsoft and Symantec agree on Egairtigado, while other detections use generic or conflicting family names.
- behaviour.hasMaliciousSandboxVerdict=false, and the completed sandbox recorded no contacted domains, IPs, or URLs.
- droppedChildren.hasMaliciousChild=false, but all 5 inspected children have unknown verdicts rather than confirmed clean results.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false — static section analysis does not indicate packed executable code.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- behaviour.hasMaliciousSandboxVerdict=false
- No network contacts were recorded in the single completed sandbox
- droppedChildren.hasMaliciousChild=false, though all five child verdicts are unknown
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false
- 24/75 antivirus detections
- Eight tier-1 engines flag the executable
- Microsoft and Symantec identify Egairtigado
- Kaspersky identifies a Trojan-Dropper
- YARA rules 'shellcode' and 'WiseInstallerStub' matched
- Runtime evidence includes T1055 and T1134
Quarantine and remove the file without executing it, while keeping endpoint protection enabled. If it already ran, perform a full scan and escalate to the security team for process, credential, and persistence review.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete24 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 12MITRE ATT&CK techniques
- 1spawned processes
- 0network contacts
- 23filesystem & 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: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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 trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
BBRWSetup.EXE
996eb82fd67c9fb9f30c1d55d4ea535f899d1d31ead4c1e5047cf0f6c4c7e4f3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\BBRWSetup.EXE"
02Isolated runtime analysis
Files
Created or changed
- Written fileObserved
GLKB42F.tmp
C:\Users\<USER>\AppData\Local\Temp\GLKB42F.tmp
03Isolated runtime analysis - Written fileObserved
GLGBFCA.tmp
C:\Users\<USER>\AppData\Local\Temp\GLGBFCA.tmp
04Isolated runtime analysis - +1 more recorded observation in Analyst mode
4 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\Users\<USER>\AppData\Local\Temp\GLKB42F.tmp
- C:\Users\<USER>\AppData\Local\Temp\GLGBFCA.tmp
- C:\Users\<USER>\AppData\Local\Temp\~GLH0000.TMP
- C:\Users\<USER>\AppData\Local\Temp\~GLH0001.TMP
- C:\Windows\system32\GLBSINST.%$D
- C:\Users\<USER>\AppData\Local\Temp\GLBBFB9.tmp
- C:\Users\<USER>\AppData\Local\Temp\GLFBFDA.tmp
- C:\Users\<USER>\AppData\Local\Temp\GLFC049.tmp
- C:\Windows\system32\GLBSINST.%$D
- C:\Users\user\AppData\Local\Temp\GLBDD4D.tmp
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 2efe9a54c8eb878711d9…8ec616Never scannednever seen before
- 50e7a30e1825fab93b94…7443c9Never scannednever seen before
- 35e805f931277a2eefb3…3383f0Never scannednever seen before
- adf8dea5d36b58cf621e…5e54a4Never scannednever seen before
- 2b8bd74a74b024ef3bd2…af5c78Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 24 / 75engines flagged
- 140sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
24 of 75 antivirus engines flagged the file, including alibabacloud and Avast.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 2 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: BBRWSetup.EXE — 996eb82fd67c9fb9f30c1d55d4ea535f899d1d31ead4c1e5047cf0f6c4c7e4f3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\BBRWSetup.EXE"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: GLKB42F.tmp — C:\Users\<USER>\AppData\Local\Temp\GLKB42F.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: GLGBFCA.tmp — C:\Users\<USER>\AppData\Local\Temp\GLGBFCA.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- shellcode
- WiseInstallerStub
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\user\Desktop\BBRWSetup.EXE"
24 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- BBRWSetup.EXE
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 38.3 MB
- Last analyzed
- Sep 14, 2026, 3:10 AM UTC
996eb82fd67c9fb9f30c1d55d4ea535f899d1d31ead4c1e5047cf0f6c4c7e4f3Safety & 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.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- 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.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- 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.
Is BBRWSetup.EXE malware?
What is BBRWSetup.EXE?
How many antivirus engines detected BBRWSetup.EXE?
I already downloaded and ran BBRWSetup.EXE — what should I do?
How do I remove BBRWSetup.EXE?
What kind of malware is BBRWSetup.EXE?
What is the SHA-256 hash of BBRWSetup.EXE?
How up to date is this analysis of BBRWSetup.EXE?
Community
Member reviews and reports for this exact file hash.