Is menu_Ru.exe safe?
Five tier-1 engines flag this packed, unsigned executable as the Pomal/Bifrost backdoor family.
13 of 75 engines detect the sample, five of them tier-1, converging on the Pomal family. Sandbox evidence shows process injection (T1055) and direct-IP network activity from a high-entropy UPX-packed binary with no code signature.
28829cee8af284d1cc…951f19d685986aRecommended 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.
13 of 75 engines detect the sample, five of them tier-1, converging on the Pomal family. Sandbox evidence shows process injection (T1055) and direct-IP network activity from a high-entropy UPX-packed binary with no code signature.
The combination of tier-1 consensus on the Pomal family, runtime evidence mapped to T1055 process-injection behavior, and the classic unsigned-packed-dropper profile outweighs the file's age and low submission count. No trusted signer or benign RAG precedent exists to offset the detections. Contacted-host reputation data is unavailable, but the remaining signals are decisive.
What We Detected
Thirteen of 75 engines flag the file, five tier-1 engines agreeing on the Pomal/Bifrost family. The binary is UPX-packed (entropy 7.93 in UPX1), unsigned, and exhibits process-injection (T1055) plus direct-IP network traffic in sandbox analysis.
Threat Behavior
Runtime traces show the sample writing temporary files, creating mutexes, and contacting multiple external IPs without domain names—consistent with a dropper or stager that hides its payload until execution.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and remove or quarantine the sample. If the file appeared on a production system, perform a full forensic review for persistence mechanisms and lateral movement.
- Unsigned executable
- High-entropy packed code
- Process-injection technique observed
- Direct-IP network traffic
- Rare submission history
Quarantine or delete the file; maintain current antivirus definitions and avoid running unsigned executables from untrusted sources.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete13 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial16 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete4 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
- 9spawned processes
- 16network contacts
- 13filesystem & 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.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Manipulated how the operating system loads code, which can redirect 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.
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 remote-access malware works
This opens a secret 'back door' into your computer. Once it's running, an attacker can control your PC from anywhere — see your screen, read your files, switch on your webcam, install more malware, or use your machine to attack others.
Bottom line:It's built to stay hidden and keep that connection open for as long as possible.
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
menu_Ru.exe
28829cee8af284d1cc7cf9b58719d2800d2d74225fa3ef2917951f19d685986a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\28829cee8af284d1cc7cf9b58719d2800d2d74225fa3ef2917951f19d685986a.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
04Isolated runtime analysis - Written fileObserved
Microsoft Compatibility Appraiser
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:0:1010:0:400:1:10
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.69.140.28
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- a83f:8110:0:1010:0:400:1:10
- 20.69.140.28
- 23.196.145.221
- 104.98.118.152
- 20.24.121.134
- a83f:8110:0:0:b00:b00:2800:1800
- 192.168.0.53
- 20.99.133.109
- 104.71.214.69
- a83f:8110:0:0:100:0:1800:0
- C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\Users\user\AppData\Local\Temp\MMBPlayer
- Local\__DDrawExclMode__
- Local\__DDrawCheckExclMode__
- Local\DDrawWindowListMutex
- Local\DDrawDriverObjectListMutex
- DDrawWindowListMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 4rule hits recorded
- 13 / 75engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
13 of 75 antivirus engines flagged the file, including alibabacloud and ClamAV.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 3 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: menu_Ru.exe — 28829cee8af284d1cc7cf9b58719d2800d2d74225fa3ef2917951f19d685986a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\28829cee8af284d1cc7cf9b58719d2800d2d74225fa3ef2917951f19d685986a.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: drwtsn32.log — C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Microsoft Compatibility Appraiser — C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:0:1010:0:400:1:10 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.69.140.28 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: backdoor
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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.
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\program.exe"PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code sectionThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidencea83f:8110:0:1010:0:400:1:10 · 20.69.140.28 · 23.196.145.221Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidencea83f:8110:0:1010:0:400:1:10
13 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- menu_Ru.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 487.5 KB
- Last analyzed
- Aug 31, 2026, 5:52 PM UTC
28829cee8af284d1cc7cf9b58719d2800d2d74225fa3ef2917951f19d685986aSafety & 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
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- 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 menu_Ru.exe malware?
What is menu_Ru.exe?
How many antivirus engines detected menu_Ru.exe?
I already downloaded and ran menu_Ru.exe — what should I do?
How do I remove menu_Ru.exe?
What kind of malware is menu_Ru.exe?
What is the SHA-256 hash of menu_Ru.exe?
How up to date is this analysis of menu_Ru.exe?
Community
Member reviews and reports for this exact file hash.