Is SMWoS.exe safe?
Zero detections across 76 engines, valid Activision signature, and prior safe signer match outweigh packing and revoked-certificate flags.
No antivirus engine flagged the file. The executable carries a verified Activision Publishing signature and matches a previously safe sample from the same signer. Sandbox and child-file checks returned no malicious indicators.
25dcfac8c94f9a9ba5…14823c96e3f9b0Recommended 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.
No antivirus engine flagged the file. The executable carries a verified Activision Publishing signature and matches a previously safe sample from the same signer. Sandbox and child-file checks returned no malicious indicators.
All 76 engines returned clean results, including 17 tier-1 engines. The certificate is valid and the single similar-hash record also carries the same signer and a safe verdict. Sandbox execution produced no malicious verdict and no malicious dropped children were found. While the file is packed with UPX and the certificate has been revoked, these static indicators alone do not override the unanimous clean engine consensus and signer history.
What We Detected
76 engines scanned the sample; none returned a malicious or suspicious result. The PE is signed by Activision Publishing with a verified certificate, though the certificate has since been revoked. One prior sample signed by the same publisher was previously classified safe.
Threat Behavior
Sandbox execution recorded process-injection techniques (T1055) and direct-IP connections, but no malicious verdict was issued. Seven dropped files were inspected and none were flagged malicious. No command-and-control domains were observed.
What To Do Now
The file can be executed in a controlled environment if needed, but keep endpoint protection enabled. Monitor for any unexpected behaviour and re-scan if the certificate revocation status changes or new detections appear.
Where this verdict could be wrong2 caveats
- contactedHosts is null — host-reputation cross-check was not completed, so no complete network reputation result is available.
- tags include 'revoked-cert' and 'upx', peAnalysis.likelyPacked=true — packing and revoked certificate raise suspicion despite clean engine results.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 76 engines
- Verified Activision Publishing signature
- Prior safe verdict for same signer
- High-entropy packed sections (UPX)
- Revoked code-signing certificate
- Process-injection technique observed in sandbox
Treat as low risk based on current evidence; continue normal security hygiene and re-evaluate if new detections emerge.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial8 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
- 14MITRE ATT&CK techniques
- 5spawned processes
- 8network 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
SMWoS.exe
25dcfac8c94f9a9ba57cdc3edb7bef49d42617fcba244951cc14823c96e3f9b0
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\25dcfac8c94f9a9ba57cdc3edb7bef49d42617fcba244951cc14823c96e3f9b0.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\wuapihost.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
~gs2252.tmp
C:\Documents and Settings\Administrator\Local Settings\Temp\~gs2252.tmp
04Isolated runtime analysis - Written fileObserved
7438wrfiles.~lk
C:\Documents and Settings\Administrator\Local Settings\Temp\7438wrfiles.~lk
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.184.37
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.229.211.108
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.
- 20.99.184.37
- 192.229.211.108
- 192.168.0.44
- 20.99.133.109
- 23.213.37.172
- 192.168.0.1
- 192.168.0.65
- 184.27.218.92
- C:\Documents and Settings\Administrator\Local Settings\Temp\~gs2252.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\7438wrfiles.~lk
- C:\Documents and Settings\Administrator\Local Settings\Temp\9213wradata.~lk
- C:\Documents and Settings\Administrator\Local Settings\Temp\~fspi.ico
- C:\Documents and Settings\Administrator\Local Settings\Temp\1030wrd.~lk\~fspi.ico
- %USERPROFILE%\AppData\Local\Temp\~gs4708.tmp
- %USERPROFILE%\AppData\Local\Temp\~fspi.ico
- %USERPROFILE%\AppData\Local\Temp\501Bwrd.~lk\~fspi.ico
- %USERPROFILE%\AppData\Local\Temp\501Bwrd.~lk\9316wrdata.~lk\swfdatar0
- %USERPROFILE%\AppData\Local\Temp\501Bwrd.~lk\9316wrdata.~lk\swfdata0
- {1B655094-FE2A-433c-A877-FF9793445069}
- Global\mchMixCache$304
- Global\Mutex, mAH, Process $00000304, API $75904064
- ZonesCounterMutex
- ZonesCacheCounterMutex
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache.
- 12cc2fd3ae8ab138ead3…b8bc2aNever scannednever seen before
- ee21f72f81a2270592e8…1dbfa7Never scannednever seen before
- 59a569de0c5ef0802d7f…d066f7Never scannednever seen before
- b803db66f492a14ee28b…905a19Never scannednever seen before
- 5b87960f5656836ca9c9…659504Never scannednever seen before
- 32a8799f55c9d45fda42…589ae4Never scannednever seen before
- 646364d12a1096fbe833…bb6f93Never 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 / 76engines flagged
- 55sources 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 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from Activision Publishing.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: SMWoS.exe — 25dcfac8c94f9a9ba57cdc3edb7bef49d42617fcba244951cc14823c96e3f9b0
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\25dcfac8c94f9a9ba57cdc3edb7bef49d42617fcba244951cc14823c96e3f9b0.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\wuapihost.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ~gs2252.tmp — C:\Documents and Settings\Administrator\Local Settings\Temp\~gs2252.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 7438wrfiles.~lk — C:\Documents and Settings\Administrator\Local Settings\Temp\7438wrfiles.~lk
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.184.37 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.229.211.108 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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%SAMPLEPATH%\25dcfac8c94f9a9ba57cdc3edb7bef49d42617fcba244951cc14823c96e3f9b0.exeThe 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.
Evidence20.99.184.37 · 192.229.211.108 · 20.99.133.109
0 of 76 engines flagged this file
View all 76 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- SMWoS.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Activision Publishing
- Size
- 4.9 MB
- Last analyzed
- Aug 8, 2026, 7:34 AM UTC
25dcfac8c94f9a9ba57cdc3edb7bef49d42617fcba244951cc14823c96e3f9b0Safety & 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 SMWoS.exe safe?
What is SMWoS.exe?
How many antivirus engines detected SMWoS.exe?
Is SMWoS.exe digitally signed?
What is the SHA-256 hash of SMWoS.exe?
Is it safe to run SMWoS.exe?
How up to date is this analysis of SMWoS.exe?
Community
Member reviews and reports for this exact file hash.