Is EditKit-1.0.14-Windows.zip safe?
One sandbox reported malware-like execution with four offensive MITRE techniques, outweighing the absence of detections across all 75 antivirus engines.
The archive produced a malicious sandbox result and runtime mappings to process injection, destructive activity, service modification, and defense impairment. Although 0 of 75 engines detected it and no examined child was confirmed harmful, the observed execution warrants containment rather than normal use.
f19398c16d6fd5aa05…402f2dac13f2b1Recommended next actions
Before opening or extracting
Do not open or extract it. Delete this archive from the device, then empty the Recycle Bin or Trash.
If you already opened or extracted it
Close it. If it opened links, requested credentials, or triggered unexpected behavior, disconnect from the internet and run a full device scan.
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 archive produced a malicious sandbox result and runtime mappings to process injection, destructive activity, service modification, and defense impairment. Although 0 of 75 engines detected it and no examined child was confirmed harmful, the observed execution warrants containment rather than normal use.
One completed sandbox assigned a malicious runtime result to the archive. The recorded execution mapped to T1055, T1485, T1543.002, and T1562.001, including possible process injection and defense impairment. Static scanning strongly disagrees: 0 of 75 engines flagged the file, including all 17 tier-1 contributors. Ten dropped children were checked without a confirmed harmful result, but each child remained unclassified rather than established as benign. The three contacted domains had no cached adverse reputation, while the observed IP addresses were not covered by that cross-check. The runtime finding therefore controls the decision, though the static disagreement leaves a meaningful false-positive possibility.
What We Detected
A completed sandbox run returned a malicious result. Runtime evidence mapped activity to T1055, T1485, T1543.002, and T1562.001, covering possible process injection, destructive behavior, service modification, and impairment of defenses.
Threat Behavior
The archive launched batch files, Windows Script Host, and local browser content from a temporary directory. A process-injection heuristic also fired, although the saved evidence does not prove the exact injection mechanism. None of 75 antivirus engines detected the archive, and all 17 tier-1 engines were silent. Ten dropped files were examined without a confirmed harmful child, but all ten remained unclassified. The three contacted domains had no cached adverse reputation; the observed IP addresses were not covered by that cross-check.
What To Do Now
Do not run the archive on a production system. Keep endpoint protection enabled, quarantine the file, and obtain a fresh copy only from the developer's verified release channel before retesting in an isolated environment.
Where this verdict could be wrong4 caveats
- No antivirus engine flagged the sample: 0/75, including 17 tier-1 engines reporting no detection.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children lacked a conclusive verdict.
- contactedHosts inspected the three observed domains and found no cached malicious or suspicious domain, but the observed IP addresses were not covered by that result.
- externalIntel.malwareBazaar.hit=false and externalIntel.circl.hit=false; YARAify coverage was unavailable because the request timed out.
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/75 antivirus engines reported a detection
- 17 tier-1 engines reported no detection
- droppedChildren.hasMaliciousChild=false
- No cached adverse reputation for the three contacted domains
- MalwareBazaar and CIRCL returned no hits
- behaviour.hasMaliciousSandboxVerdict=true
- Four offensive runtime mappings: T1055, T1485, T1543.002, T1562.001
- MalwareTips.Synth.ProcessInjection heuristic fired
- Windows Script Host executed commands.js from a temporary extraction path
- File was first submitted only four days earlier
Quarantine the archive and avoid executing it on production devices. Keep security protections enabled and verify the package against a hash or signed release published through the developer's official channel.
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
Partial3 of 6 contacted hosts were cross-checked; coverage is incomplete.
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
- 14MITRE ATT&CK techniques
- 15spawned processes
- 6network contacts
- 15filesystem & 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: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Runs hidden system commands (script or shell).
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.
Moderate concern: Checks which security software you have installed.
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 trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
EditKit-1.0.14-Windows.zip
f19398c16d6fd5aa0583f1a404467b21d19795dd3f67775345402f2dac13f2b1
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\EditKit-1.0.14/Install EditKit - Windows.bat^"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\EditKit-1.0.14/Install EditKit - Windows.bat
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
b1be10f4-3ed6-4211-af82-a1f5715cf7d7
C:\ProgramData\Microsoft\Windows\WER\Temp\b1be10f4-3ed6-4211-af82-a1f5715cf7d7
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
edge-mobile-static.azureedge.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
business.bing.com
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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- edge-mobile-static.azureedge.net
- business.bing.com
- assets.msn.com
- 150.171.109.183
- 150.171.73.13
- 162.159.36.2
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows Script\Settings\Telemetry\wscript.exe\JScriptSetScriptStateStarted
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\b1be10f4-3ed6-4211-af82-a1f5715cf7d7
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\8a64c099-0c6b-4e9e-979d-bf313ff4d01c
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 2c213a5d80ea29b77a89…976aecNever scannednever seen before
- 857203bd571e97a005bb…e85eceNever scannednever seen before
- 4fa5a33a850ebe909240…7ce0a7Never scannednever seen before
- 125a173cd8bd4a168df0…c76320Never scannednever seen before
- 7dbd9db0cfa5d2120df0…727a6cNever scannednever seen before
- 0b0d697316d809ec4e42…ab499dNever scannednever seen before
- 09b0b380b3d95ea27d50…e6869bNever scannednever seen before
- b5e9378d433e60e65d8c…0f0e4aNever scannednever seen before
- d7c7b1d78b6421e9bf2e…76db56Never scannednever seen before
- cc7af757ca93c951ad44…e105d0Never 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
- 0 / 75engines flagged
- 74sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: EditKit-1.0.14-Windows.zip — f19398c16d6fd5aa0583f1a404467b21d19795dd3f67775345402f2dac13f2b1
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\EditKit-1.0.14/Install EditKit - Windows.bat^"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\EditKit-1.0.14/Install EditKit - Windows.bat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: b1be10f4-3ed6-4211-af82-a1f5715cf7d7 — C:\ProgramData\Microsoft\Windows\WER\Temp\b1be10f4-3ed6-4211-af82-a1f5715cf7d7
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: edge-mobile-static.azureedge.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: business.bing.com — 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
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\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\EditKit-1.0.14/Install EditKit - Windows.bat^"
0 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
- EditKit-1.0.14-Windows.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 1.0 MB
- Last analyzed
- Sep 28, 2026, 2:22 PM UTC
f19398c16d6fd5aa0583f1a404467b21d19795dd3f67775345402f2dac13f2b1Safety & 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 open or extract this archive. Delete this archive from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already opened or extracted 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 you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the original trusted source and verify its exact hash when possible.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is EditKit-1.0.14-Windows.zip a virus?
What is EditKit-1.0.14-Windows.zip?
How many antivirus engines detected EditKit-1.0.14-Windows.zip?
What should I do if I already opened or extracted EditKit-1.0.14-Windows.zip?
How do I remove EditKit-1.0.14-Windows.zip?
What kind of malware is EditKit-1.0.14-Windows.zip?
What is the SHA-256 hash of EditKit-1.0.14-Windows.zip?
How up to date is this analysis of EditKit-1.0.14-Windows.zip?
Community
Member reviews and reports for this exact file hash.