Chapter 02
Why we think so
2 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This Win32 DLL had no detections from any of the 70 antivirus engines that checked it, including all 18 major antivirus engines. Four sandbox runs recorded no rare offensive behaviour and no malicious contacts. Its self-signed signature failed verification, which is neutral rather than a positive.
None of the 70 antivirus engines that checked it flagged the file, and all 18 major antivirus engines that reported returned clean. The four sandbox runs show rundll32 loading the DLL and calling il2cpp baselib exports, which fits a Unity runtime support library. The only notable sandbox mapping is Process Injection, but no target process was recorded, and that mapping appears on many clean files. The signature claims a self-signed publisher and failed verification, so we give it no credit. No reference database lists the file as malicious, and the one contacted host is the analysis VM's own background traffic.
What we detected
None of the 70 antivirus engines that checked it flagged this Win32 DLL, and 18 of 18 major antivirus engines reported it clean. MalwareBazaar, YARAify and CIRCL returned no hits.
Threat behavior
Four sandbox runs recorded the DLL being loaded through rundll32 and its exported il2cpp baselib functions being called. No rare offensive techniques, dropped files, persistence indicators or named injection targets were recorded. The one contacted host is background traffic from the analysis environment. The file is a medium-prevalence sample, submitted by 176 sources, with normal section entropy and no packer. Its self-signed certificate does not chain to a trusted root and is treated as unsigned.
What to do now
The evidence does not point to malicious behaviour. Normal caution still applies: treat a DLL from an unknown source with care, and keep your security software enabled.
Where this verdict could be wrong3 caveats
- The signature failed verification (self-signed, untrusted root), so the signer name carries no trust.
- No static analysis of the uploaded bytes was run, so the DLL's contents were not inspected directly; the assessment relies on engine, sandbox and reference-database results.
- The sandbox mapped Process Injection, though without any recorded target process.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 70 antivirus engines that checked it flagged it, including all 18 major antivirus engines
- No rare offensive behaviours across four sandbox runs
- No hits in MalwareBazaar, YARAify or CIRCL
- No packer and normal section entropy
- The signature is self-signed and failed verification, so it does not identify a trustworthy author.
- The file was not uploaded for direct inspection, so its contents were not examined by our own analysis.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 4 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 4isolated sandbox runs
- 18sandbox rule tags
- 15spawned processes
- 0network contacts
- 25filesystem & mutex artifacts
Runtime behaviour
What this file did when executed
This file was detonated in 4 sandboxes and its runtime behaviour was observed.
Techniques observed in the sandbox
18MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1016· Network recon
- T1027· Obfuscated code
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1056· Keylogging
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1218.011
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1542.003
- T1553
- T1553.002
- T1574· Execution hijack
Observed activity
Processes started
15Programs the file ran, with their command lines.
rundll32.exe"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\library.dll",#1loaddll64.exeC:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\attachment.dll"cmd.exeC:\Windows\System32\cmd.exe cmd.exe /C rundll32.exe "C:\Users\user\Desktop\attachment.dll",#1rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",#1rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\attachment.dll,??0AbortShim@il2cpp_baselib@@QEAA@P6A_NW4Baselib_ErrorCode@1@PEAX@Z1@Zrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\attachment.dll,??0Thread@il2cpp_baselib@baselib@@QEAA@$$QEAV012@@Z
Show all 15 entries for processes started
rundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe C:\Users\user\Desktop\attachment.dll,??0Thread@il2cpp_baselib@baselib@@QEAA@XZrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",??0AbortShim@il2cpp_baselib@@QEAA@P6A_NW4Baselib_ErrorCode@1@PEAX@Z1@Zrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",??0Thread@il2cpp_baselib@baselib@@QEAA@$$QEAV012@@Zrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",??0Thread@il2cpp_baselib@baselib@@QEAA@XZrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",?detail_AssertLogMute@il2cpp_baselib@@YAX_N@Zrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",?detail_AssertLog@il2cpp_baselib@@YAXPEBDZZrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",?YieldExecution@Thread@il2cpp_baselib@baselib@@SAXXZrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",?TryJoin@Thread@il2cpp_baselib@baselib@@QEAA_NV?$duration@IU?$ratio@$00$0DOI@@std@@@chrono@std@@@Zrundll32.exeC:\Windows\System32\rundll32.exe rundll32.exe "C:\Users\user\Desktop\attachment.dll",?SupportsThreads@Thread@il2cpp_baselib@baselib@@SA_NXZ
Files
15Files the file created, changed or deleted.
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\09e1b697-373b-4a36-adf9-5121fd9c5dc0 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportQueue - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\64e15bc9-c3b8-4288-9858-e23e0ad0bbc7 - Written
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\0004dd0c-437c-4e23-9a2b-faa78c51b472
Show all 15 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\06445b9d-18b8-4a0f-94b7-42208ba135e3 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\1466305c-0b81-4141-af3f-96ddd0ca6710 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\169fa89a-9afd-4cf5-97f9-2ec5304f3082 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\2cd0bee6-2f24-4efa-b91b-df385be983d1 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\46ca2eb4-417c-4e56-a394-a011444896dd - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\51471b36-eb7a-4edf-a5cd-b09f56f008f9 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\515f0248-1bb9-4c9e-acb8-e581ddba0070 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\5515e0ce-a02c-415b-afc7-4854f12fdae2 - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\5fa442da-8bd1-450e-a99b-f38aeb136bb5
Registry and auto-start
1Settings the file changed, including ways to start again after a restart.
- Set
\REGISTRY\A\{7d850578-c1ad-faf0-1c44-f210fd4c96cd}\Root\InventoryApplicationFile\PermissionsCheckTestKey
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6192\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex6644\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6288\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex6524\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess672\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex6728
Show all 10 entries for mutexes
\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess2312\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex6692\Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6672\Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex5272
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
atm.teams.mira.tm.svc.cloud.microsoft
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; a signature that did not verify.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Nov 18, 2026, 12:49 AM UTC
- SHA-256
a2449487c8b1f3bf98bf02c358f51fe227af73ded97d6d6203eeeb283cb56fd9- SHA-1
a6b8bb5b76f0b2bd67f6ffc4694805b4f8d83966- MD5
3ed6169b2bc2334a288148327d601f72
About this file
baselib.dll is a Win32 DLL file of 230.3 kB.
- Type and size
- Win32 DLL · 230.3 kB
- Signer
- Project C.A.R.L. (self-signed) (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Oct 8, 2026On VirusTotal.
- Submitted by
- 176 distinct sources
- Packer
- None detected
- Entropy
- 6.08 of 8
First scanned
Antivirus consensus
0 of 70 engines flagged this file
5 of the 75 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-235 engines0flagged
- Low-trust17 engines0flagged
View all 75 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
- GoogleNo result
- 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
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Rule-based evidence
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
Evidence
T1055 (sandbox MITRE mapping)
PE forensics
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.
Prevalence
How widely this file has been seen
Widely uploaded, but first seen within the last six months. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is baselib.dll safe?
What is baselib.dll?
How many antivirus engines detected baselib.dll?
Is baselib.dll digitally signed?
What is the SHA-256 hash of baselib.dll?
Is it safe to use baselib.dll?
How up to date is this analysis of baselib.dll?
Community
Member reviews and reports for this exact file hash.