Is shinobinewera.exe safe?
No antivirus engine detected this widely submitted executable, although one sandbox mapped possible process injection and defense-impairment activity that warrants source verification.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, after more than 32,000 submissions from 3,721 sources. One sandbox mapped possible process injection and defense impairment, but issued no malicious runtime finding, and complete checks found no harmful contacted hosts or dropped children.
d028af14184de4e9fc…0753ee7f964186Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, after more than 32,000 submissions from 3,721 sources. One sandbox mapped possible process injection and defense impairment, but issued no malicious runtime finding, and complete checks found no harmful contacted hosts or dropped children.
The strongest evidence is the absence of detections across 75 antivirus engines, including all 17 reporting tier-1 engines. The executable is also widely established, with 32,783 submissions from 3,721 sources over 277 days, which makes an undetected widespread threat less likely. A completed sandbox did map T1055 and T1562.001, so the runtime evidence is not entirely routine. However, the sandbox issued no malicious verdict, all five observed network hosts were fully checked without a malicious or suspicious reputation hit, and none of ten inspected child files was identified as malicious. The unsigned status reduces publisher assurance, but it does not outweigh the broad detection and prevalence evidence here.
What We Detected
No detections were reported by 75 antivirus engines, including 17 tier-1 engines. The file has broad historical exposure, with 32,783 submissions from 3,721 sources over 277 days. It is unsigned, so its publisher cannot be authenticated through a code-signing certificate.
Threat Behavior
One completed sandbox run mapped activity to T1055 (Process Injection) and T1562.001 (Impair Defenses). Those mappings are concerning, but the sandbox did not issue a malicious verdict. Reputation checks covered all five observed domains and found no malicious or suspicious hosts, while ten inspected child files produced no identified malicious child. Static PE analysis also found no high-entropy code or likely packing.
What To Do Now
Obtain the executable from its expected original source and verify its SHA-256 hash before running it. Keep endpoint protection enabled, and avoid execution if the file arrived unexpectedly or its source cannot be established.
Where this verdict could be wrong3 caveats
- The completed sandbox mapped activity to T1055 process injection and T1562.001 impairment of defenses; these are meaningful risk indicators despite lacking engine, host, or child-file corroboration.
- signing.applicable=true but signing.signed=false, so no authenticated publisher identity supports the executable.
- similarHashes shows 1/2 prior verdicts 'suspicious' for this imphash (matchKind=imphash, signerCoMatch=false), though imphash-only matches may reflect a shared build framework.
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 antivirus engines reported a detection
- All 17 tier-1 engines reported no detection
- 32,783 submissions from 3,721 sources over 277 days
- All five observed contacted hosts were checked with no malicious or suspicious hits
- No malicious child among 10 inspected dropped files
- Unsigned Win32 executable with no authenticated publisher
- Sandbox telemetry mapped possible process injection (T1055)
- Sandbox telemetry mapped possible defense impairment (T1562.001)
Use the file only if it came from the expected original source and its SHA-256 hash matches a trusted release. Keep antivirus and endpoint protection enabled during any execution.
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
Complete5 contacted hosts were cross-checked.
YARA
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 11MITRE ATT&CK techniques
- 8spawned processes
- 5network contacts
- 40filesystem & mutex artifacts
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.
- svc.ha-teams.office.com
- svc.ms-acdc-teams.office.com
- assets.msn.com
- assets.msn.com-ion.edgesuite.net
- a1666.dscr.akamai.net
- \REGISTRY\A\{4edea6f9-ea89-5cf4-1297-ffe501b56917}\Root\InventoryApplicationFile\WritePermissionsCheck
- \REGISTRY\A\{4edea6f9-ea89-5cf4-1297-ffe501b56917}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\ProgramId
- \REGISTRY\A\{4edea6f9-ea89-5cf4-1297-ffe501b56917}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\FileId
- \REGISTRY\A\{4edea6f9-ea89-5cf4-1297-ffe501b56917}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\LowerCaseLongPath
- \REGISTRY\A\{4edea6f9-ea89-5cf4-1297-ffe501b56917}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\LongPathHash
- \REGISTRY\A\{4edea6f9-ea89-5cf4-1297-ffe501b56917}\Root\InventoryApplicationFile\file.exe|3bfeaaf1919d30b\Name
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\ca8825e7-dafb-4a82-a878-f6d28746b390
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\07f17f03-f2dc-4d01-be72-7f5ca1a512ee
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF74.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE10B.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD84F.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF74.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess6560
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\514dafe5-12b5-4ef0-8721-481bd4fe41f3
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess3336
- \Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex5144
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 6988d58618fa4e768c2a…740af9Never scannednever seen before
- 3645ac38d52055a6e6e0…5c16bdNever scannednever seen before
- 8040b669d097cc00b4ea…d0e70bNever scannednever seen before
- cca18f1e87d119e3d0c8…b3471bNever scannednever seen before
- a8b608ddef16b7c593ea…9d4ba5Never scannednever seen before
- c4bb63f84a0134bc9ff4…ff0230Never scannednever seen before
- cb3deac73ef84243ef7d…d853ddNever scannednever seen before
- 6b9789561f08b817df62…d45112Never scannednever seen before
- 962a5e8342228244e48b…dcef1eNever scannednever seen before
- 0f24d2af7b7647142ee3…cd6268Never 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 3,721sources 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 has a long, established submission history across 3,721 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: shinobinewera.exe — d028af14184de4e9fc400fa9cd713d8536ce9f60e0c9ff93dd0753ee7f964186
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 6560 -s 456
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ca8825e7-dafb-4a82-a878-f6d28746b390 — C:\ProgramData\Microsoft\Windows\WER\Temp\ca8825e7-dafb-4a82-a878-f6d28746b390
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: svc.ha-teams.office.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: svc.ms-acdc-teams.office.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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:\Users\<USER>\Desktop\file.exe"
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
- shinobinewera.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 102.0 KB
- Last analyzed
- Oct 8, 2026, 1:27 PM UTC
d028af14184de4e9fc400fa9cd713d8536ce9f60e0c9ff93dd0753ee7f964186Safety & 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
Run it only when it came 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 shinobinewera.exe safe?
What is shinobinewera.exe?
How many antivirus engines detected shinobinewera.exe?
What is the SHA-256 hash of shinobinewera.exe?
Is it safe to run shinobinewera.exe?
How up to date is this analysis of shinobinewera.exe?
Community
Member reviews and reports for this exact file hash.