Is sims-4-updater-v2.6.6.exe safe?
Signed executable flagged by tier-1 engine as HackTool:Win64/Malgent with process-injection and LSASS access observed.
6 of 75 engines flag the file, including Microsoft tier-1 detection HackTool:Win64/Malgent!MSR. Sandbox shows T1055 process injection, LSASS access, and direct-IP traffic. The signer 'Sims4Updater' has no prior reputation and the imphash matches prior suspicious samples.
59a6741c57b772f497…08711926b79c61Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
6 of 75 engines flag the file, including Microsoft tier-1 detection HackTool:Win64/Malgent!MSR. Sandbox shows T1055 process injection, LSASS access, and direct-IP traffic. The signer 'Sims4Updater' has no prior reputation and the imphash matches prior suspicious samples.
Microsoft's tier-1 detection plus Gridinsoft's matching label satisfy hacktoolConfirmed criteria. Observed MITRE techniques T1055, T1485, T1486 are offensive and corroborated by sandbox telemetry. The signer lacks any historical samples, weakening any benign interpretation. Similar imphash files previously received suspicious verdicts, and no external-intel or dropped-child evidence contradicts the malicious signals.
What We Detected
6 of 75 engines report malicious, one of them tier-1 (Microsoft). The sample is signed by an unknown 'Sims4Updater' entity with an invalid certificate. Sandbox execution revealed process injection (T1055), data-wiping attempts (T1485/T1486), and LSASS memory access.
Threat Behavior
The binary contacted two raw IP addresses and wrote multiple PyInstaller-extracted files. No malicious children were dropped and external-intel sources returned no hits, but the offensive techniques alone meet hacktool criteria.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and remove the sample. If the file was downloaded from an official Sims 4 mod site, report the link to the site administrators.
Where this verdict could be wrong1 caveat
- prevalence.classification=common_new with 1312 submitters may indicate legitimate distribution despite offensive techniques.
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 malicious dropped children
- No external-intel corroboration
- Tier-1 engine labels it a confirmed hacktool
- Process injection and LSASS access observed
- Unknown signer with no reputation history
- Direct-IP network traffic without domain context
Treat as malicious; delete the file and scan the system for any persistence mechanisms left behind.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete6 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 18MITRE ATT&CK techniques
- 12spawned processes
- 2network contacts
- 31filesystem & 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: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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.
Threat context
How hacktools are abused
This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.
Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.
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.6.exe
59a6741c57b772f49721af8eb99a60aee6a9c5c79ede8f831f08711926b79c61
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\sims-4-updater-v2.6.6.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\_MEI55122\81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI55122\VCRUNTIME140.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
185.199.111.133
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
- 185.199.111.133
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI55122\81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI55122\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI55122\VCRUNTIME140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI55122\_asyncio.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI55122\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\k0a4n9mf
- C:\Users\<USER>\Desktop\tmp_file_0
- C:\Users\<USER>\Desktop\updater_remote.cache_tmp
- C:\Users\<USER>\Desktop\updater_tmp\downloading\Base Game 1.119.109.1020 0.zip.001.aria2
- C:\Users\<USER>\Desktop\updater_tmp\downloading\Base Game 1.119.109.1020 0.zip.001.aria2_partial
- 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
- 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
- 76f6bc85fc9cb89bc3f9…5415eaNever 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.
- 3rule hits recorded
- 6 / 75engines flagged
- 1,312sources 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
6 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1,596 times from 1,312 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: sims-4-updater-v2.6.6.exe — 59a6741c57b772f49721af8eb99a60aee6a9c5c79ede8f831f08711926b79c61
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\sims-4-updater-v2.6.6.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\_MEI55122\81d243bd2c585b0f4821__mypyc.cp313-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI55122\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 185.199.111.133 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
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.
Evidence"C:\Windows\system32\NOTEPAD.EXE" C:\Users\<USER>\Desktop\updater_readme.txtSandbox 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.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.
Evidence185.199.111.133 · 162.159.36.2
6 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- sims-4-updater-v2.6.6.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: Sims4Updater
- Size
- 25.2 MB
- Last analyzed
- Sep 4, 2026, 3:57 PM UTC
59a6741c57b772f49721af8eb99a60aee6a9c5c79ede8f831f08711926b79c61Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If any of your files were locked or renamed, do NOT pay the ransom — payment rarely restores files. Recover them from a backup instead.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is sims-4-updater-v2.6.6.exe a virus?
What is sims-4-updater-v2.6.6.exe?
How many antivirus engines detected sims-4-updater-v2.6.6.exe?
What should I do if I already ran sims-4-updater-v2.6.6.exe?
How do I remove sims-4-updater-v2.6.6.exe?
What kind of malware is sims-4-updater-v2.6.6.exe?
Is sims-4-updater-v2.6.6.exe digitally signed?
What is the SHA-256 hash of sims-4-updater-v2.6.6.exe?
How up to date is this analysis of sims-4-updater-v2.6.6.exe?
Community
Member reviews and reports for this exact file hash.