File scan report
Verdict Suspicious
Is sims- 4- updater- v2. 4. 11. exe safe? Treat it as suspicious.
Two less reliable engines flagged the file while 17 major antivirus engines remained silent.
Why Suspicious? 2 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as untrusted; do not run without additional verification from official Sims-4-updater channels or updated vendor signatures.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
2 of 70 flagged
- Flagged 2
- No detection 68
- No result 4
- Code signing Signer not verified
- Test run Completed
- First seen 10mo ago
Chapter 02
Why we think so
2 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The engine profile matches an AV-on-AV false-positive pattern, but the absence of any trusted-publisher history and the presence of offensive MITRE techniques prevent a clean verdict. Prevalence data indicates the binary has circulated for months among many users, lowering the chance of a targeted attack. Without a completed host-reputation check or corroborating major detections, the evidence remains mixed.
What We Detected
The file is signed by an unknown 'Sims4Updater' certificate with no prior history. Sandbox execution recorded MITRE techniques T1055 (process injection), T1485/T1486 (data destruction/encryption), and direct-IP contact to 104.21.52.91.
Threat Behavior
The single contacted IP lacks a completed reputation cross-check.
What To Do Now
Keep security software enabled. Avoid executing the file until a trusted source or updated signatures provide clearer classification.
Where this verdict could be wrong2 caveats
- communityComments contain mixed researcher verdicts (two 'Malicious', one 'Clean', one 'Suspicious') — no consensus.
- contactedHosts is null; no complete host-reputation cross-check available for the single IP 104.21.52.91.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 17 major antivirus engines clean
- Common_old prevalence (1125 sources)
- No malicious files it created
- Less reliable engine detections
- Self-signed certificate with no history
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 15sandbox rule tags
- 8spawned processes
- 1network contact
- 30filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 6: FileSeen in the test run
sims-4-updater-v2.4.11.exe
a48ef2d0d7a9d5d5ca9dea6e7017140e682b0eb6d15c33ace93c7f8666e746d3
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
software.exe
"C:\Users\<USER>\Desktop\software.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
NOTEPAD.EXE
"C:\Windows\system32\NOTEPAD.EXE" C:\Users\<USER>\Desktop\updater_readme.txt
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
mfc140u.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI54922\Pythonwin\mfc140u.dll
Test run - Evidence 5 of 6: Written fileSeen in the test run
win32ui.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI54922\Pythonwin\win32ui.pyd
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
104.21.52.91
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
Includes 15 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
2 of the 70 antivirus engines that checked it flag it; a signature that did not verify.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 2
- APEXMalicious
- WebrootW32.Hack.Tool
File fingerprint
- Last analyzed
- Sep 7, 2026, 6:05 PM UTC
- SHA-256
a48ef2d0d7a9d5d5ca9dea6e7017140e682b0eb6d15c33ace93c7f8666e746d3- SHA-1
3c4c6e8701ff4cf723b64ede89dfe867925d2183- MD5
52b234520c47115173fa9fc33395b551
About this file
sims-4-updater-v2.4.11.exe is a Win32 EXE file of 21.1 MB.
- Type and size
- Win32 EXE · 21.1 MB
- Signer
- Sims4Updater (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Dec 29, 2025On VirusTotal.
- Submitted by
- 1,125 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Includes every engine result (74), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is sims-4-updater-v2.4.11.exe safe, or is it malware?
What is sims-4-updater-v2.4.11.exe?
How many antivirus engines detected sims-4-updater-v2.4.11.exe?
What should I do if I already ran sims-4-updater-v2.4.11.exe?
Is sims-4-updater-v2.4.11.exe digitally signed?
What is the SHA-256 hash of sims-4-updater-v2.4.11.exe?
How up to date is this analysis of sims-4-updater-v2.4.11.exe?
Community
Member reviews and reports for this exact file hash.