MalwareTipsTools

File scan report

Scan another file

Verdict Malicious

Analyzed , 4 hours ago

Is Poison Menu.dll safe? No, we rate this exact file malicious.

Sixteen of the 71 antivirus engines that checked it flagged this unsigned DLL, including three major detections, with repeated Yogi labels and a corroborating malicious runtime…

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Don't use this component

If you already used 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 used it

  1. Don't use this component. Let your antivirus remove this component, then repair or reinstall the program it belongs to from its official website. Don't delete or replace the file by hand.

If you already used 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.

Why we think so

Share this file report

Poison Menu.dll: Malicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Antivirus results

16 of 71 flagged

  • Flagged 16
  • No detection 55
  • No result 4
FilePoison Menu.dll4.5 MBSHA-256 59a47d40d940…f20007
  • Code signing Unsigned
  • Test run Completed
  • First seen 9d ago
A sandbox test run rated its behaviour as malicious.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

This unsigned DLL drew 16 detections from 75 engines, including BitDefender, ESET-NOD32, and Microsoft. Several engines repeatedly identify Yogi, and one runtime result reported malware, although another was clean; keep the file quarantined and do not load it.

Where this verdict could be wrong4 caveats
  • Another sandbox result was clean, so the runtime findings do not form a consensus.
  • Most engines did not flag the file, including several major antivirus products.
  • Four of five files with the same import-table fingerprint previously received safe decisions, but none had a matching signer and such fingerprints can be shared by unrelated software.
  • No malware-specific community rules or public sample-database entries matched the hash.

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 not needed or not applicable. See every source

Chapter 03

What it did in our test

It ran in 4 isolated tests; 1 test environment rated what it did as risky.

Test run summary

Capture complete
  • 4isolated sandbox runs
  • 18sandbox rule tags
  • 4spawned processes
  • 0network contacts
  • 1filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • 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: Unpacked hidden content while it ran.

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

  • Note: Read the user name of the test computer.

  • Note: Deleted files or logs during the test run (installers often clean up after themselves).

  • Note: Read basic details of the test computer, such as its Windows version.

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

  • Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

  • Not confirmed: A sandbox rule tagged this run as loading code in memory; nothing confirms it.

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

A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, 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.

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 4: FileSeen in the test run

      Poison Menu.dll

      59a47d40d940705f1678bde0dc1847f543d221fbb3c7e6be81ebd9f7b3f20007

      Uploaded file

  2. Processes

    What ran

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

      rundll32.exe

      "C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\Poison.Menu.dll",#1

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

      loaddll32.exe

      C:\Windows\System32\loaddll32.exe loaddll32.exe "C:\Users\user\Desktop\Poison.Menu.dll"

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

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

      Connect

      \Device\ConDrv\\Connect

      Test run

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

Chapter 04

Technical details

16 of the 71 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

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

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 16 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxCompleteWorth noting: 4 runs: 1 malicious, 1 clean, 2 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesCompleteNo rule matched
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 16

  • BitDefender (major engine)Gen:Variant.Yogi.102722
  • Emsisoft (major engine)Gen:Variant.Yogi.102722 (B)
  • ESET-NOD32 (major engine)MSIL/GameHack_AGen.ES potentially unsafe application
  • GData (major engine)Gen:Variant.Yogi.102722
  • Microsoft (major engine)Trojan:Win32/Wacatac.C!ml
  • AhnLab-V3Malware/Win.Generic.C5928457
  • ALYacGen:Variant.Yogi.102722
  • ArcabitTrojan.Yogi.D19142
8 more in the full engine list

File fingerprint

Last analyzed
Nov 1, 2026, 10:26 PM UTC
SHA-256
59a47d40d940705f1678bde0dc1847f543d221fbb3c7e6be81ebd9f7b3f20007
SHA-1
3ffbbde641014180edbdef9d83f48309e119444b
MD5
3e9a30e5e14a16ee100f2b53dfb05f7d

About this file

Poison Menu.dll is a Win32 DLL file of 4.5 MB.

Claims to be
Poison MenuFrom the file's own version information, written by whoever built it.
Original name
Poison Menu.dllMatches the shared file name.
Type and size
Win32 DLL · 4.5 MB
Signer
UnsignedNo code signature.
First seen
Oct 23, 2026On VirusTotal.
Submitted by
14 distinct sources
Packer
None detected
Entropy
7.26 of 8

First scanned

Chapter 05

Questions & answers

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

Is Poison Menu.dll malware?
Yes. This copy of Poison Menu.dll (SHA-256 59a47d40…0007) is malicious. Other files with the same name can be different, so check the hash. Don't use it. Let your antivirus remove this component, then repair or reinstall the program it belongs to from its official website. Don't delete or replace the file by hand. 16 of the 71 antivirus engines that checked it flag it. Antivirus engines classify it as a trojan: malware disguised as something harmless so that you run it. If you've already used it, see the steps below.
What is Poison Menu.dll?
Poison Menu.dll is a Windows library (DLL), about 4.5 MB. Its version information says it is “Poison Menu”. Version information is written by whoever built the file, so it is a claim, not proof of who made it. VirusTotal first saw it on Oct 23, 2026.
How many antivirus engines detected Poison Menu.dll?
16 of the 71 antivirus engines that checked it flag Poison Menu.dll, including Microsoft and ESET. We weigh which engines flagged it and what else the scan found, not just the count. A sandbox test run also rated its behaviour as malicious.
I already downloaded and used Poison Menu.dll — 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 Poison Menu.dll?
To remove Poison Menu.dll: 1) run a full scan with your antivirus and let it remove what it finds. 2) Let your antivirus remove this component, then repair or reinstall the program it belongs to from its official website. Don't delete or replace the file by hand. 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 Poison Menu.dll?
Antivirus engines classify Poison Menu.dll as a trojan: malware disguised as something harmless so that you run it.
What is the SHA-256 hash of Poison Menu.dll?
The SHA-256 fingerprint of Poison Menu.dll is 59a47d40d940705f1678bde0dc1847f543d221fbb3c7e6be81ebd9f7b3f20007, and its MD5 is 3e9a30e5e14a16ee100f2b53dfb05f7d. 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 Poison Menu.dll?
This report reflects the scan on Nov 1, 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.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
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.