File scan report
Verdict Safe
Is apisetstub safe? Yes, no threats found.
Small Microsoft-signed Windows API-set stub DLL with zero detections across 74 engines, a long widespread history, and a reference-database match as a known system component.
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
No action is needed. This is a normal Microsoft runtime stub library that is safe to keep.
Good practice2 tips
We found nothing harmful in this file.
Use it only as part of a program you got from the developer's own website.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 4
- Code signing Microsoft Corporation
- Test run Completed
- First seen 8y ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This is a small 64-bit Windows API-set stub library with a verified Microsoft signature. None of the 70 antivirus engines that checked it flagged it, and it has been seen by 584 sources since 2018. It also appears in a reference database of known software files.
None of the 70 antivirus engines that checked it flagged the file, and all 17 major antivirus engines that reported returned no detection. The DLL carries a verified Microsoft Corporation signature that matches our curated trusted-publisher list, and earlier Microsoft-signed files in our records were clean. It matches a reference-database entry for an API-set forwarding DLL and is widely distributed. In our single sandbox run, the only notable activity was the Windows crash reporter firing when the stub was loaded on its own, which is expected for a forwarding library. A third-party comment suggesting otherwise was untrusted and is contradicted by the other evidence.
What We Detected
A 18,696-byte 64-bit DLL with a verified Microsoft Corporation signature. It matches a reference-database entry for a Windows API-set stub (api-ms-win-core-debug-l1-1-0.dll). None of the 70 antivirus engines that checked it flagged it, and it has been seen by 584 sources since 2018.
Threat Behavior
No offensive techniques were observed. When the DLL was loaded directly, the sandbox showed rundll32 starting and Windows Error Reporting logging a crash. That is normal for a stub library with no real exports. Our host-reputation check was not completed.
What To Do Now
No action is needed. This is a standard Windows runtime component. Keep your antivirus enabled and up to date.
Where this verdict could be wrong2 caveats
- One community annotation reports a third-party 'likely malicious' result, but that comment field was flagged as untrusted, and another sandbox annotation plus our own sandbox run reported clean.
- Our host-reputation cross-check was not completed, so we have no complete reputation result for any network contacts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Verified Microsoft Corporation signature
- No detections from any of the 74 antivirus engines
- Matches a known-software reference database entry
- Widely seen across hundreds of sources since 2018
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- 13sandbox rule tags
- 9spawned processes
- 0network contacts
- 40filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
13MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1036
- T1045
- T1057· Lists programs
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1129· Loads modules
- T1198
- T1218.011
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1574.002· Execution hijack
Observed activity
Processes started
9Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\init.dll",#1loaddll64.exeC:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\readme.dll"cmd.exeC:\Windows\System32\cmd.exe cmd.exe /C rundll32.exe "C:\Users\user\Desktop\readme.dll",#1rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\readme.dll",#1rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\readme.dll,DebugBreakrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\readme.dll,IsDebuggerPresent
Show all 9 entries for processes started
rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\readme.dll,OutputDebugStringArundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\readme.dll",DebugBreakrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\readme.dll",IsDebuggerPresent
Files
30Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\473d3039-733b-4e2b-92bf-64f9a0be9b5d - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\21bba5dd-4643-48f6-8834-7de93a1a5ad3 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\f4ab73eb-1a6f-482c-9979-16edcc03d4eb
Show all 30 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\dc8c4271-3b89-496b-ad94-b4f079e3b19c - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\d6fd4479-04fe-4f38-86e1-f1fd2e85c806 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\f1255671-2b67-4a27-8d13-23617d1ffeba - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBE.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4482.tmp.WERInternalMetadata.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER45FA.tmp.xml - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFA8.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFA8.tmp.dmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFE6.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBE.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4482.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER45FA.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FBE.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4482.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER45FA.tmp.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFA8.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFA8.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFE6.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFE6.tmp.dmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD074.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD074.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD0E2.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD101.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERE95A.tmp
Registry and auto-start
19Settings the file changed, including ways to start again after a restart.
- Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\WritePermissionsCheck - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProgramId - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\FileId - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LowerCaseLongPath - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LongPathHash - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Name
Show all 19 entries for registry and auto-start
- Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\OriginalFileName - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Publisher - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\Version - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\BinFileVersion - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\BinaryType - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProductName - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\ProductVersion - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\LinkDate - Set
\REGISTRY\A\{cc2be570-7469-07b0-f44c-97b2e0832b79}\Root\InventoryApplicationFile\rundll32.exe|c8d854bf61fafc41\BinProductVersion - Deleted
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{11517B7C-E79D-4e20-961B-75A811715ADD} - Deleted
\REGISTRY\A\{f8dccffe-7d10-91d5-65dc-02acf3983e7b}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Deleted
\REGISTRY\A\{5d617c75-d7ba-6b96-da4b-1fb4bb9e66ab}\Root\InventoryApplicationFile\PermissionsCheckTestKey - Deleted
\REGISTRY\A\{c0c578e7-2d55-d861-f497-1014e4e30efc}\Root\InventoryApplicationFile\PermissionsCheckTestKey
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
Local\WERReportingForProcess3792Global\AmiProviderMutex_InventoryApplicationFileGlobal\611bb49b-38ac-426e-aac6-39c525094ebc\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7628\Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile\Sessions\1\BaseNamedObjects\Global\e373cd97-ee59-42d1-a619-923b2faeccd1
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7640\Sessions\1\BaseNamedObjects\Global\010696db-553c-40c3-a873-23b65a150192\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7924\Sessions\1\BaseNamedObjects\Global\2813fd8e-9412-4a71-9dd7-bfca9bdb8e5a
Sandbox background — not the file
6The analysis machine's own processes and connections, recorded in every run.
- VM process
WerFault.exeC:\Windows\system32\WerFault.exe -u -p 3792 -s 500 - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM process
WerFault.exeC:\Windows\System32\WerFault.exe C:\Windows\system32\WerFault.exe -u -p 7640 -s 308 - VM process
WerFault.exeC:\Windows\System32\WerFault.exe C:\Windows\system32\WerFault.exe -u -p 7628 -s 304 - VM process
WerFault.exeC:\Windows\System32\WerFault.exe C:\Windows\system32\WerFault.exe -u -p 7924 -s 316 - VM process
WerFault.exeC:\Windows\System32\WerFault.exe C:\Windows\system32\WerFault.exe -u -p 8004 -s 320
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- c8c7e6514011e61a61e7…f3e97bNot checkedno saved verdict
- 0d8c288be5550ab76003…aed46cNot checkedno saved verdict
- e670a3addd0005c7030c…9e05c9Not checkedno saved verdict
- 314770f7f3ef7d32144a…39a9c5Not checkedno saved verdict
- c0215f2ee3a2cae78787…44c659Not checkedno saved verdict
- c1bf6d84475c3a7d8991…2dada3Not checkedno saved verdict
- b7e8e06c8be95cc4e511…cc226bNot checkedno saved verdict
- 2ca926b8f98a8a283f1c…00793fNot checkedno saved verdict
- ac203ffb857b317e545e…6edc39Not checkedno saved verdict
- e763ace1755868a44eb2…2d81f9Not checkedno saved verdict
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; signed by Microsoft Corporation.
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.
File fingerprint
- Last analyzed
- Oct 16, 2026, 11:40 PM UTC
- SHA-256
55574f9e80d313048c245acefd21801d0d6c908a8a5049b4c46253efaf420f89- SHA-1
e7c8a6c29c3158f8b332eea5c33c3b1e044b5f73- MD5
9476affaac53e6e34405c4001f141805
About this file
apisetstub is a Win32 DLL file of 18.7 kB.
- Type and size
- Win32 DLL · 18.7 kB
- Signer
- Microsoft CorporationValid code signature.
- First seen
- May 12, 2018On VirusTotal.
- Submitted by
- 584 distinct sources
- Packer
- None detected
- Entropy
- 3.10 of 8
First scanned
Antivirus consensus
0 of 70 engines flagged this file
4 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust16 engines0flagged
View all 74 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
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.
These identify the compiler, runtime or installer used to build the file. They are not packing and are not a risk signal on their own.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is apisetstub safe?
What is apisetstub?
How many antivirus engines detected apisetstub?
Is apisetstub digitally signed?
What is the SHA-256 hash of apisetstub?
Is it safe to use apisetstub?
How up to date is this analysis of apisetstub?
Community
Member reviews and reports for this exact file hash.