Is TikFuckerV4.2 (1).zip safe?
A tier-1 Godosesz detection, defense-evasion activity, and direct-IP traffic make this newly observed ZIP risky despite limited antivirus consensus.
Three of 74 engines flagged this newly observed archive, with Ikarus naming Godosesz. Runtime evidence includes T1562.001 and contact with 172.67.72.57, but there is no complete host-reputation result, no sandbox malware verdict, and no confirmed malicious child.
ceccbe859bcddbb6b2…77809a84d84b87Recommended 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 of 74 engines flagged this newly observed archive, with Ikarus naming Godosesz. Runtime evidence includes T1562.001 and contact with 172.67.72.57, but there is no complete host-reputation result, no sandbox malware verdict, and no confirmed malicious child.
Ikarus identified Virus.Win64.Godosesz, providing one high-trust family signal among 3 of 74 detections. The sandbox observed T1562.001, a defense-impairment technique, along with direct-IP communication to 172.67.72.57. That IP was not fully reputation-checked because contactedHosts is unavailable, so the network signal remains unresolved. Counter-evidence includes 16 tier-1 engines without detections, no sandbox malware verdict, and no external research-rule matches. Because the archive is newly observed and every inspected child remains unclassified, the combined evidence warrants isolation rather than execution.
What We Detected
Three of 74 antivirus engines flagged the ZIP. Ikarus, a tier-1 engine, named Virus.Win64.Godosesz; Google returned an unspecified detection, and Bkav used a generic malware label. The archive has only one recorded submission and no established reputation.
Threat Behavior
One sandbox run extracted and launched executable content from the archive. It observed T1562.001, associated with impairing defenses, plus direct-IP contact to 172.67.72.57. No complete host-reputation result is available for that address, and the sandbox did not issue a malware verdict. Eight extracted children were inspected, but all remain unclassified.
What To Do Now
Do not open or run the archive on a production system. Keep endpoint protection enabled, quarantine the file, and obtain it again only from a verified source if it is expected software.
Where this verdict could be wrong4 caveats
- Only 1 tier-1 engine detected Godosesz, while 16 tier-1 engines reported no detection and tier1FamilyConsensus.strong=false.
- behaviour.hasMaliciousSandboxVerdict=false, so the completed sandbox run did not issue a malware verdict.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false, although CIRCL coverage failed.
- No inspected child was confirmed malicious, but all 8 child verdicts were unknown rather than benign.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 3/74 engines detected the archive.
- tier1FamilyConsensus.strong=false, with only one tier-1 family vote.
- behaviour.hasMaliciousSandboxVerdict=false.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false.
- droppedChildren.hasMaliciousChild=false.
- Ikarus identified Virus.Win64.Godosesz.
- The archive is newly observed with only one submission.
- Sandbox activity included T1562.001 defense impairment.
- Direct-IP communication occurred with 172.67.72.57.
- All 8 extracted child files remain unclassified.
Quarantine the ZIP and avoid executing its contents unless the source and purpose can be independently verified. Keep endpoint protection enabled and rescan the archive and extracted executables when additional intelligence becomes available.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 6MITRE ATT&CK techniques
- 5spawned processes
- 1network contacts
- 13filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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
TikFuckerV4.2 (1).zip
ceccbe859bcddbb6b28b17c3ff83bd24bb21478ab815d67e6277809a84d84b87
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\ComboMaker.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\TikFuckerV4.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
sh5s4xzk.1nv
C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv
04Isolated runtime analysis - Written fileObserved
ComboMaker.exe
C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv\ComboMaker.exe
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.67.72.57
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 172.67.72.57
- C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv
- C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv\ComboMaker.exe
- C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv\TikFuckerV4.exe
- C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv\config.yml
- C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv\data
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- 2ccd27f627596b842e78…792c9aNever scannednever seen before
- 01f5e64883b5b47a16da…9d2c55Never scannednever seen before
- efe93161ccbe4a645d1f…790be5Never scannednever seen before
- 99451f97905d2bce0616…d2a4c2Never scannednever seen before
- bbeacfc6bdf79e4fa3cd…b668ceNever scannednever seen before
- f2c27b7bcf39fd65f337…da8bf6Never scannednever seen before
- 9ed6a5bc899519b84e1d…3fc961Never scannednever seen before
- c6ad1de9af53f5fa0fbd…917125Never 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.
- 1rule hit recorded
- 3 / 74engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 of 74 antivirus engines flagged the file, including Bkav and Google.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: TikFuckerV4.2 (1).zip — ceccbe859bcddbb6b28b17c3ff83bd24bb21478ab815d67e6277809a84d84b87
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\AppData\Local\Temp\ComboMaker.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\TikFuckerV4.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: sh5s4xzk.1nv — C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ComboMaker.exe — C:\Users\user\AppData\Local\Temp\sh5s4xzk.1nv\ComboMaker.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 172.67.72.57 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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.
Evidence172.67.72.57
3 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 3 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- TikFuckerV4.2 (1).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 21.3 MB
- Last analyzed
- Sep 16, 2026, 1:04 AM UTC
ceccbe859bcddbb6b28b17c3ff83bd24bb21478ab815d67e6277809a84d84b87Safety & 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 TikFuckerV4.2 (1).zip safe, or is it malware?
What is TikFuckerV4.2 (1).zip?
How many antivirus engines detected TikFuckerV4.2 (1).zip?
I already downloaded and opened or extracted TikFuckerV4.2 (1).zip — what should I do?
How do I remove TikFuckerV4.2 (1).zip?
What kind of malware is TikFuckerV4.2 (1).zip?
What is the SHA-256 hash of TikFuckerV4.2 (1).zip?
How up to date is this analysis of TikFuckerV4.2 (1).zip?
Community
Member reviews and reports for this exact file hash.