Is AssaultCube_v1.3.0.2_LockdownEdition.exe safe?
No antivirus engine detected this widely submitted, years-old installer, and its completed sandbox run produced no malware verdict despite one token-related technique.
The sample drew 0 detections from 75 antivirus engines and has been submitted more than 3,000 times since 2022. One sandbox observed T1134 among mostly common installer and application activity, but produced no malware verdict; the executable remains unsigned, and host-reputation coverage was incomplete.
77eff4497232562eeb…21234045ee61a5Recommended 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.
The sample drew 0 detections from 75 antivirus engines and has been submitted more than 3,000 times since 2022. One sandbox observed T1134 among mostly common installer and application activity, but produced no malware verdict; the executable remains unsigned, and host-reputation coverage was incomplete.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including no tier-1 family consensus. The file also has broad, long-standing prevalence, with 2,634 sources and 3,183 submissions since April 2022. A completed sandbox run recorded one offensive technique, T1134, alongside 18 techniques common in ordinary software, without producing a malware verdict. No malicious child was identified, although all ten dropped files remained inconclusive. The executable is unsigned and the host-reputation check did not cover every observed contact, so downloading it from the official project channel remains important.
What We Detected
No antivirus engine flagged the sample: 0 of 75 reported it as malicious or suspicious, and no tier-1 engine identified a malware family. The file is also well established, with 2,634 distinct sources and 3,183 submissions since April 2022. No supporting hit appeared in the available researcher-rule or hash-intelligence checks.
Threat Behavior
One completed sandbox run observed T1134, a token-related technique that can be used offensively, together with 18 techniques commonly seen in installers and ordinary applications. The sandbox did not issue a malware verdict. Ten dropped files were checked and none was identified as malicious, but all ten remained without conclusive child verdicts. The host-reputation cross-check covered only part of the observed domains and IP addresses, so no complete network-reputation conclusion is available.
What To Do Now
Use a copy obtained from the official AssaultCube project release channel and verify its SHA-256 value as 77eff4497232562eeb1862f97d484777202e8ac42c411093a821234045ee61a5. Keep endpoint protection enabled, particularly because this Windows executable is unsigned.
Where this verdict could be wrong5 caveats
- signing.applicable=true and signing.signed=false — the executable has no verified publisher identity.
- T1134 was observed during execution; token manipulation can be offensive, although it was not accompanied by a malicious sandbox verdict.
- Only 42 engines produced results while 28 timed out, reducing the strength of the 0/75 detection result.
- The contacted-host cross-check inspected 5 hosts but did not cover every distinct observed domain and IP.
- Ten dropped children were inspected, but droppedChildren.rollup.unknown=10 means none received a conclusive child verdict.
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 of 75 antivirus engines reported a malicious or suspicious result.
- No tier-1 engine identified a malware family.
- The sample has 3,183 submissions from 2,634 sources dating to 2022.
- The completed sandbox run produced no malware verdict.
- No packing or high-entropy code was identified.
- The Windows executable is unsigned and has no verified publisher identity.
- Sandbox execution observed token manipulation technique T1134.
- Only 42 engines completed reporting, while 28 timed out.
- Host-reputation coverage did not include every observed domain and IP.
- All 10 dropped children remained inconclusive.
Use only the official project release and confirm the SHA-256 hash before running it. Keep antivirus and endpoint protection enabled because the executable lacks a verified signature.
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
Partial5 of 25 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
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
- 19MITRE ATT&CK techniques
- 14spawned processes
- 25network contacts
- 30filesystem & 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.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- fp2e7a.wpc.phicdn.net
- fp2E7A.wpc.2BE4.phicdn.net
- arc.msn.com
- 204.79.197.203
- 23.216.147.64
- 23.216.147.76
- 20.99.132.105
- 20.62.24.77
- 20.99.184.37
- 13.107.4.50
- 192.229.211.108
- 20.99.133.109
- 20.99.186.246
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService127.0.6490.0\Start
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService127.0.6490.0\ImagePath
- HKLM\SOFTWARE\Microsoft\Windows Media Player NSS\3.0\Servers\A70D59A1-8EAD-4F40-AAAB-FBFC460800A4\FriendlyName
- C:\Users\<USER>\AppData\Local\Temp\nsn67BA.tmp
- C:\Users\<USER>\AppData\Local\Temp\welcome.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsc67CA.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsc67CA.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsc67CA.tmp\System.dll
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB6.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB7.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE63.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE62.tmp.csv
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c5c7ba4a7a85170df5e3…ce291aNever scannednever seen before
- 56b96add1978b1abba28…753fe2Never scannednever seen before
- 5ab7051c0b5c2f383360…540241Never scannednever seen before
- 8dc562cda7217a3a52db…7f65a8Never scannednever seen before
- 42dd4dda3249a94e32e2…cd2fb7Never scannednever seen before
- fd6e24bfdb956c2d5d33…c10150Never scannednever seen before
- 04c3de104ae6d6c3635e…c0594bNever scannednever seen before
- 60cbb386e8a8fb46a087…a16b80Never scannednever seen before
- 0434a40352d3cace7bf5…aae853Never scannednever seen before
- 38c0b24155c9c2c22b06…bd5a7cNever 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.
- 0rule hits recorded
- 0 / 75engines flagged
- 2,634sources 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 2,634 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 3,183 times from 2,634 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AssaultCube_v1.3.0.2_LockdownEdition.exe — 77eff4497232562eeb1862f97d484777202e8ac42c411093a821234045ee61a5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\AssaultCube_v1.3.0.2_LockdownEdition.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsn67BA.tmp — C:\Users\<USER>\AppData\Local\Temp\nsn67BA.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: welcome.bmp — C:\Users\<USER>\AppData\Local\Temp\welcome.bmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- AssaultCube_v1.3.0.2_LockdownEdition.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 46.0 MB
- Last analyzed
- Oct 6, 2026, 5:28 AM UTC
77eff4497232562eeb1862f97d484777202e8ac42c411093a821234045ee61a5Safety & 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 AssaultCube_v1.3.0.2_LockdownEdition.exe safe?
What is AssaultCube_v1.3.0.2_LockdownEdition.exe?
How many antivirus engines detected AssaultCube_v1.3.0.2_LockdownEdition.exe?
What is the SHA-256 hash of AssaultCube_v1.3.0.2_LockdownEdition.exe?
Is it safe to run AssaultCube_v1.3.0.2_LockdownEdition.exe?
How up to date is this analysis of AssaultCube_v1.3.0.2_LockdownEdition.exe?
Community
Member reviews and reports for this exact file hash.