File scan report
Verdict Malicious
Is steam_ api. dll safe? No, we rate this exact file malicious.
This unsigned Steam-related DLL is confirmed crack tooling, with 38 of the 70 antivirus engines that checked it flagging it and evidence from the test run mapping activity to…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Keep it only if you installed it on purpose for security testing. Otherwise delete it and run a full antivirus scan.
What to do now4 steps
This is a hacking tool. It is risky to keep and run, but finding it is not by itself a sign that the device is infected.
What to do
Don't use it unless you got it on purpose for security testing on systems you own. 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 didn't put it on the device yourself, delete it and run a full antivirus scan: something else may have brought it.
Tools like this often come with cracked or pirated software. If it came that way, treat the whole download as unsafe and scan everything it installed.
If you already used it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
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
38 of 70 flagged
- Flagged 38
- No detection 32
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 11y ago
Chapter 02
Why we think so
6 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The DLL is identified as crack or hacking tool software by multiple engines, including ESET-NOD32, while Microsoft and other vendors apply trojan labels. One completed sandbox run mapped activity to process injection, and the file has no authenticated publisher to offset those findings.
Thirty-eight of the 70 antivirus engines that checked it flagged the sample, including six independent major detections. ESET-NOD32 specifically identified Win32/HackTool.Crack.EE, while additional engines corroborated crack-tool labeling, satisfying the confirmed-hacktool criterion. A completed sandbox run mapped activity to process injection and recorded execution through rundll32.exe. The file is unsigned and has no established signer history. Although it is old and commonly submitted, and no sandbox supplied an explicit malware verdict, those mitigating points do not outweigh the confirmed offensive-tool classification and broad engine detections. Reputation for the observed IP was not fully checked because no complete contacted-host result is available.
What We Detected
38 of the 70 antivirus engines that checked it flagged this unsigned Win32 DLL. Six major antivirus engines detected it, with ESET-NOD32 naming Win32/HackTool.Crack.EE, Fortinet naming Riskware/Crack.A, and Microsoft naming Trojan:Win32/Skeeyah.A. Multiple corroborating crack-tool labels make this more than an isolated generic alert.
Threat Behavior
One completed sandbox observation mapped activity to MITRE T1055, Process Injection, and recorded execution through rundll32.exe. The sample also wrote files beneath C:\ProgramData\SkidRow. It contacted the IP address 204.79.197.203, but no complete host-reputation result is available, so that connection cannot be characterized as benign or malicious from this evidence.
What To Do Now
Do not load or distribute this DLL, particularly as part of a game crack or modified Steam installation. Keep security software enabled, let your antivirus remove the file, remove the associated cracked software, and obtain the game or application from its official distribution channel. If the DLL already ran, perform a full system scan and review related processes and files.
Where this verdict could be wrong3 caveats
- prevalence shows 599 submitters and 648 submissions since 2015, indicating this is an old, widely encountered sample rather than a file.
- No sandbox returned a malicious verdict, although the completed run still recorded and this field alone does not establish benign behavior.
- The absence of community YARA matches and the absence of a known-software database match provide no researcher-curated corroboration, but absence of those hits may reflect coverage limits.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The sample has been observed since 2015 and submitted 648 times
- No explicit malicious sandbox verdict was recorded
- No malicious file it created was identified
- CIRCL and YARAify returned no corroborating hit
- 38/70 antivirus detections
- Six major antivirus engines detections
- Confirmed crack/hacking tool labeling
- Unsigned Win32 DLL
- Execution through rundll32.exe
- No complete reputation check for contacted IP 204.79.197.203
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 our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 8sandbox rule tags
- 1spawned processes
- 0network contacts
- 4filesystem & 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 basic details of the test computer, such as its Windows version.
Note: Checked which security software was installed 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: A sandbox rule tagged this run as contacting a server, but no contacted host 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 hacking tools are used
Hacking tools are programs that can switch off security software, test passwords or attack other computers. Security professionals use them on purpose; criminals also bundle them with malware.
Bottom line:Keep it only if you installed it on purpose, and check how it got onto the device if you didn't.
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 4: FileSeen in the test run
steam_api.dll
e0a8ac90ca0cb856e24230bc1a5193b67cdf661d09984750edfe703d0aa859be
Uploaded file
- 1
Processes
What ran
- Evidence 2 of 4: ProcessSeen in the test run
rundll32.exe
"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\library.dll",#1
Test run
- 2
Files
Created or changed
- Evidence 3 of 4: Written fileSeen in the test run
SkidRow
C:\ProgramData\SkidRow\
Test run - Evidence 4 of 4: Written fileSeen in the test run
0
C:\ProgramData\SkidRow\0
Test run - +1 more recorded observation
4 facts from the test run. See the full activity list.
Includes 8 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
38 of the 70 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.
Engines that flagged it 38
- ESET-NOD32 (major engine)Win32/HackTool.Crack.EE potentially unsafe application
- Fortinet (major engine)Riskware/Crack.A!tr
- Microsoft (major engine)Trojan:Win32/Skeeyah.A!bit
- Sophos (major engine)Mal/VMProtBad-A
- Symantec (major engine)ML.Attribute.HighConfidence
- TrellixENS (major engine)GenericRXNI-WP!9868ED91A953
- TrendMicro (major engine)TROJ_GEN.R002C0OEO21
- TrendMicro-HouseCall (major engine)TROJ_GEN.R002C0OEO21
File fingerprint
- Last analyzed
- Sep 9, 2026, 12:19 PM UTC
- SHA-256
e0a8ac90ca0cb856e24230bc1a5193b67cdf661d09984750edfe703d0aa859be- SHA-1
0261f11bd0004ebc645029d124cae92421d86e4f- MD5
9868ed91a9531ab4592c82a7df33dbbb
About this file
steam_api.dll is a Win32 DLL file of 154.6 kB.
- Type and size
- Win32 DLL · 154.6 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 27, 2015On VirusTotal.
- Submitted by
- 599 distinct sources
- Packer
- None detected
- Entropy
- 7.72 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers 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 steam_api.dll a virus?
What is steam_api.dll?
How many antivirus engines detected steam_api.dll?
What should I do if I already used steam_api.dll?
How do I remove steam_api.dll?
What kind of program is steam_api.dll?
What is the SHA-256 hash of steam_api.dll?
How up to date is this analysis of steam_api.dll?
Community
Member reviews and reports for this exact file hash.