Is sims-4-updater-v2.6.4 (1).zip safe?
ZIP contains a PyInstaller executable that exhibits process-injection and LSASS-access behaviour, yet only three low-tier engines flag it.
Three engines flag the archive; sandbox shows T1055, T1486 and LSASS access. No tier-1 consensus or malicious children exist, leaving the file in mixed-signal territory.
d13171b317af3ee111…44ee8835a464caRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Three engines flag the archive; sandbox shows T1055, T1486 and LSASS access. No tier-1 consensus or malicious children exist, leaving the file in mixed-signal territory.
The file is a 26 MB ZIP that extracts a PyInstaller-built executable. Sandbox execution recorded process injection, credential-store access and anti-analysis tactics, yet only three engines (two low-trust, one tier-2) raised alerts. No tier-1 engine agreed on any family, no dropped child was malicious, and external-intel sources returned no hits. Medium prevalence and the absence of a complete host-reputation check keep the sample in the suspicious band.
What We Detected
Three of 75 engines flagged the ZIP: Bkav (W32.Malware), Webroot (W32.Hack.Tool) and Zillya (Backdoor.XWorm). Sandbox logs show the extracted executable touching LSASS and performing process injection (T1055) plus defence-impairment (T1562.001) and data-encryption (T1486) techniques. Ten dropped children were inspected; none carried malicious verdicts.
Threat Behavior
The observed MITRE techniques are consistent with credential-dumping or RAT tooling, but the lack of tier-1 corroboration and the medium prevalence suggest the file could also be an aggressively detected legitimate utility or cracked game mod. No external-intel or contacted-host reputation data is available to resolve the ambiguity.
What To Do Now
Do not run the extracted executable. Keep Windows Defender and other endpoint protection enabled. If the file is required, re-download it from an official Sims-4 source and compare hashes before execution.
Where this verdict could be wrong1 caveat
- Zillya labels the sample Backdoor.XWorm.Win32.3294, but no tier-1 engine corroborates the XWorm family.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 engine detections
- Zero malicious dropped children
- Medium prevalence across 798 submitters
- Sandbox observed LSASS access and process injection
- Three engines label the file malicious or hacktool
- Filename suggests game cheat or crack
Treat the archive as untrusted; do not execute the contained executable until further independent verification is obtained.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 11MITRE ATT&CK techniques
- 14spawned processes
- 0network contacts
- 17filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
sims-4-updater-v2.6.4 (1).zip
d13171b317af3ee1112a569b1a7419df4464adbe12f6a10a3a44ee8835a464ca
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\sims-4-updater-v2.6.4.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI41242\81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI41242\VCRUNTIME140.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Temp\_MEI41242\81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI41242\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI41242\VCRUNTIME140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI41242\_asyncio.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI41242\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\fprmtz3e
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never 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
- 3 / 75engines flagged
- 798sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including Bkav and Webroot.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1,021 times from 798 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: sims-4-updater-v2.6.4 (1).zip — d13171b317af3ee1112a569b1a7419df4464adbe12f6a10a3a44ee8835a464ca
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\sims-4-updater-v2.6.4.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI41242\81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI41242\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
3 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- sims-4-updater-v2.6.4 (1).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 25.1 MB
- Last analyzed
- Sep 4, 2026, 7:10 AM UTC
d13171b317af3ee1112a569b1a7419df4464adbe12f6a10a3a44ee8835a464caSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or extract it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is sims-4-updater-v2.6.4 (1).zip safe, or is it malware?
What is sims-4-updater-v2.6.4 (1).zip?
How many antivirus engines detected sims-4-updater-v2.6.4 (1).zip?
What should I do if I already opened or extracted sims-4-updater-v2.6.4 (1).zip?
How do I remove sims-4-updater-v2.6.4 (1).zip?
What kind of malware is sims-4-updater-v2.6.4 (1).zip?
What is the SHA-256 hash of sims-4-updater-v2.6.4 (1).zip?
How up to date is this analysis of sims-4-updater-v2.6.4 (1).zip?
Community
Member reviews and reports for this exact file hash.