Is tbb.dll safe?
Zero engine detections, common old file, and NSRL reference outweigh the single sandbox T1055 observation.
No antivirus engine flagged the sample. The file is a 14-year-old signed DLL with a known game product reference in NSRL. Sandbox noted process-injection API usage and direct-IP traffic, but no malicious verdict or known-bad hosts were recorded.
2280e7acdef5e2ccf2…f5836c04e12e32Recommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
No antivirus engine flagged the sample. The file is a 14-year-old signed DLL with a known game product reference in NSRL. Sandbox noted process-injection API usage and direct-IP traffic, but no malicious verdict or known-bad hosts were recorded.
All 75 engines returned clean, including 17 tier-1 engines. The Intel signer lacks historical samples in our database, yet the file's age, prevalence, and NSRL match indicate legitimate distribution. Sandbox activity (T1055, direct-IP) is consistent with game DRM or updater behaviour and produced no malicious verdict. No dropped malicious children or known-bad host contacts were found.
What We Detected
75 of 75 engines reported the file clean. The DLL is signed by 'Intel(R) Software Products' (verification status null) and matches an NSRL entry for Crusader Kings II. Sandbox execution recorded T1055 process-injection API calls and three direct-IP connections, but no malicious verdict or known-bad hosts.
Threat Behavior
No malicious sandbox verdict, no dropped malicious children, and no tier-1 or low-trust detections. The observed behaviour aligns with legitimate game components rather than malware.
What To Do Now
The file can be considered safe for normal use. Keep endpoint protection enabled and only download software from official sources.
Where this verdict could be wrong1 caveat
- CIRCL hit references NSRL modern RDS entry for 'Crusader Kings II' but does not confirm the DLL is part of that legitimate game; NSRL trust score is only 50.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines flagged malicious
- common_old prevalence with 5549-day history
- CIRCL NSRL match for known game product
Retain the file; no further action required beyond routine security hygiene.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 12MITRE ATT&CK techniques
- 2spawned processes
- 3network contacts
- 40filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
tbb.dll
2280e7acdef5e2ccf20454f11756a44e2cb3e2afd05d6d2d0ef5836c04e12e32
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\WerFault.exe -u -p 3476 -s 716
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
209caeca-2bb9-444e-bea0-8819b3b9ae5e
C:\ProgramData\Microsoft\Windows\WER\Temp\209caeca-2bb9-444e-bea0-8819b3b9ae5e
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
52.147.198.201
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
40.88.32.150
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 52.147.198.201
- 40.88.32.150
- 20.189.173.22
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\209caeca-2bb9-444e-bea0-8819b3b9ae5e
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\c6619bd1-eab1-4687-8400-c705dce66d8b
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER31B4.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER36B7.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER37B2.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER31B4.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER36B7.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess3476
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\30d5ff1c-ab52-47ff-afd3-faa6c682bd0f
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3640
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 9d597876a555771b6a8f…85e7c3Never scannednever seen before
- 0d7be90eaa2c50716274…bd5c1cNever scannednever seen before
- 98eb57eb4521e465aaec…af3078Never scannednever seen before
- e70d442ea6b2c834a4a0…b790c3Never scannednever seen before
- 070db6971144a231fb71…490d6bNever scannednever seen before
- 37e50f50b3ca3c8424b0…63eddaNever scannednever seen before
- 32a7226c8e2ba3c79f71…746a3aNever scannednever seen before
- df37669002a1ce6897a6…5a93d5Never scannednever seen before
- 36737585cc014f9e0c1b…4128fbNever scannednever seen before
- 04fb9f193af6a820d7c6…b2603cNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 366sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash appears in a known-software reference database.
Verdict inputView chapterProvenanceObservedSourceReference software databaseObserved at - 03
The hash has a long, established submission history across 366 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: tbb.dll — 2280e7acdef5e2ccf20454f11756a44e2cb3e2afd05d6d2d0ef5836c04e12e32
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\SysWOW64\WerFault.exe -u -p 3476 -s 716
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 209caeca-2bb9-444e-bea0-8819b3b9ae5e — C:\ProgramData\Microsoft\Windows\WER\Temp\209caeca-2bb9-444e-bea0-8819b3b9ae5e
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.147.198.201 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 40.88.32.150 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\readme.dll",#1The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence52.147.198.201 · 40.88.32.150 · 20.189.173.22
0 of 75 engines flagged this file
View all 75 engine results
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.
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.
Fingerprint and provenance
- File name
- tbb.dll
- Format
- Win32 DLL
- Code signing
- Signature not verified: Intel(R) Software Products
- Size
- 139.2 KB
- Last analyzed
- Sep 6, 2026, 9:11 AM UTC
2280e7acdef5e2ccf20454f11756a44e2cb3e2afd05d6d2d0ef5836c04e12e32Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Use it only as part of software obtained from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is tbb.dll safe?
What is tbb.dll?
How many antivirus engines detected tbb.dll?
Is tbb.dll digitally signed?
What is the SHA-256 hash of tbb.dll?
Is it safe to use tbb.dll?
How up to date is this analysis of tbb.dll?
Community
Member reviews and reports for this exact file hash.