File scan report

Verdict Malicious

Analyzed , 1 month ago

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

This exact file is listed in abuse.ch MalwareBazaar, a public malware-sample sharing database. 52 of the 71 antivirus engines that checked it also flag it.

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.

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

Antivirus results

52 of 71 flagged

  • Flagged 52
  • No detection 19
  • No result 4
FileSmokeAPI.dll2.7 MBSHA-256 f874fa379dc8…cf0764
  • Code signing Unsigned
  • Test run Completed
  • First seen 3y ago
1 strong detection rule matched this file.

Chapter 02

Why we think so

2 points against it and 0 in its favour, checked against the scan evidence.

Malware intelligence match

Why this file is treated as malware

The conclusion below is grounded in the recorded hash match and scan evidence.

Analyst conclusion

It was first listed on Feb 22, 2024; MalwareBazaar publishes no family name for it.

Where this verdict could be wrong1 caveat
  • MalwareBazaar accepts submissions from anyone, including automated uploads; legitimate tools bundled with malware are sometimes listed.

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
  • 17sandbox rule tags
  • 1spawned processes
  • 4network 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: Checked whether it was running on a test computer.

  • Note: Read the network settings of the test computer.

  • Note: Listed the programs running on the test computer.

  • Note: Talked to servers over the internet during the test run.

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

  • Note: Looked through folders on the test computer (most installers do this).

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

  • Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.

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

      SmokeAPI.dll

      f874fa379dc8557f5d640a17753900a7c1a1d5f93a13aeeef176316b8ccf0764

      Uploaded file
  2. Processes

    What ran

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

      rundll32.exe

      Test run
  3. Files

    Created or changed

    2
    1. Evidence 3 of 6: Written fileSeen in the test run

      Connect

      \Device\ConDrv\\Connect

      Test run
    2. Evidence 4 of 6: Dropped fileWorked out from other results

      c6456e12e5e53287a547af4103e0397cb9697e466cf75844312dc296d43d144d

      A file it created; no rating is saved for it.

      Files it created
    3. +1 more recorded observation
  4. Network

    Hosts contacted

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

      209.197.3.8

      Contacted during the test run.

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

      13.89.179.12

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

52 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 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 52 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial3 of 5 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteWorth noting: 4 community YARA rules (1 malware-specific) Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteRisk signal: Listed (no family name published)
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 52

  • Avast (major engine)Win32:MalwareX-gen [Trj]
  • AVG (major engine)Win32:MalwareX-gen [Trj]
  • Avira (major engine)TR/W32.MalwareX
  • BitDefender (major engine)Trojan.GenericKD.76999492
  • Emsisoft (major engine)Trojan.GenericKD.76999492 (B)
  • ESET-NOD32 (major engine)Win32/Agent_AGen.ALA trojan
  • F-Secure (major engine)Trojan.TR/W32.MalwareX
  • Fortinet (major engine)W32/Agent_AGen.ALA!tr
44 more in the full engine list

File fingerprint

Last analyzed
Aug 28, 2026, 8:52 PM UTC
SHA-256
f874fa379dc8557f5d640a17753900a7c1a1d5f93a13aeeef176316b8ccf0764
SHA-1
8e2f160783e159fdd33e806acbc5afb37f84ec4d
MD5
4a1a823e5cf4fb861dd6ba94539d29c4

About this file

SmokeAPI.dll is a Win32 DLL file of 2.7 MB.

Type and size
Win32 DLL · 2.7 MB
Signer
UnsignedNo code signature.
First seen
Mar 15, 2023On VirusTotal.
Submitted by
1,647 distinct sources
Packer
None detected
Entropy
6.27 of 8

First scanned Updated

Chapter 05

Questions & answers

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

Is SmokeAPI.dll a virus?
Yes. This copy of SmokeAPI.dll (SHA-256 f874fa37…0764) 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. 52 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. This exact file is also listed in MalwareBazaar, a public malware database. If you've already used it, see the steps below.
What is SmokeAPI.dll?
SmokeAPI.dll is a Windows library (DLL), about 2.7 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Mar 15, 2023.
How many antivirus engines detected SmokeAPI.dll?
52 of the 71 antivirus engines that checked it flag SmokeAPI.dll, including Microsoft and ESET. We weigh which engines flagged it and what else the scan found, not just the count. The rating also rests on a listing of this exact file in MalwareBazaar, a public malware database, and on the other evidence.
What should I do if I already used SmokeAPI.dll?
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 SmokeAPI.dll?
To remove SmokeAPI.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 SmokeAPI.dll?
Antivirus engines classify SmokeAPI.dll as a trojan: malware disguised as something harmless so that you run it.
Has SmokeAPI.dll been seen before?
Yes. This exact file is listed in MalwareBazaar, a public malware database, first listed on Feb 22, 2024. MalwareBazaar accepts uploads from anyone, including automated ones, so the listing supports the other evidence rather than proving malice on its own.
What is the SHA-256 hash of SmokeAPI.dll?
The SHA-256 fingerprint of SmokeAPI.dll is f874fa379dc8557f5d640a17753900a7c1a1d5f93a13aeeef176316b8ccf0764, and its MD5 is 4a1a823e5cf4fb861dd6ba94539d29c4. 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 SmokeAPI.dll?
This report reflects the scan on Aug 28, 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.