Is MDECloudProtectionDemoTest (1).zip safe?
Only 2 of 75 engines detected this security-demo archive, but process-injection and defense-impairment mappings warrant caution despite absent tier-1 support.
The archive has weak antivirus consensus: 2 of 75 engines flagged it, while all 17 reporting tier-1 engines remained silent. Its security-demo naming and non-malicious sandbox result suggest a likely false positive, but T1055 and T1562.001 activity plus unclassified extracted children justify handling it cautiously.
c7d76d9791767ce743…1563eec9fcfcd9Recommended 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.
The archive has weak antivirus consensus: 2 of 75 engines flagged it, while all 17 reporting tier-1 engines remained silent. Its security-demo naming and non-malicious sandbox result suggest a likely false positive, but T1055 and T1562.001 activity plus unclassified extracted children justify handling it cautiously.
Two of 75 engines raised detections, and neither came from a tier-1 engine. The completed sandbox did not issue a malicious verdict, while no inspected child was identified as malware. The filename and classifier evidence indicate a security demonstration file, which can intentionally exercise behavior that resembles an attack. Nevertheless, runtime mappings include T1055 process injection and T1562.001 defense impairment, and both extracted children remain unclassified. The balance therefore favors a defensive test artifact or false positive, but the behavioral uncertainty prevents treating it as ordinary benign software.
What We Detected
Two of 75 antivirus engines flagged the ZIP archive. NANO-Antivirus identified Joke.fisaez, while Skyhigh applied an Artemis PUP label; all 17 reporting tier-1 engines remained silent, and there was no family consensus.
Threat Behavior
One completed sandbox run mapped activity to T1055 process injection and T1562.001 impairment of defenses. The sandbox itself did not issue a malicious verdict, no persistence indicators were recorded, and neither of the two inspected children was identified as malicious; however, both child verdicts remain unknown. The two inspected host entries had no malicious or suspicious cache hits, but complete host-reputation coverage is unavailable because the observed IP was not clearly included.
What To Do Now
Treat the archive as a controlled security demonstration rather than routine software. Keep endpoint protection enabled, verify that it came from an official Microsoft security-testing channel, and only inspect or execute it in an isolated test environment.
Where this verdict could be wrong5 caveats
- T1055 process-injection and T1562.001 defense-impairment mappings are meaningful risk indicators even though the completed sandbox did not issue a malicious verdict.
- NANO-Antivirus named Joke.fisaez and Skyhigh labeled the file Artemis!PUP, so the two detections are not purely generic heuristic alerts.
- The two extracted child files remain unclassified rather than confirmed benign.
- Complete host-reputation coverage is unavailable because behaviour lists two domains and one IP, while contactedHosts reports only two inspected hosts.
- YARAify timed out, leaving a gap in researcher-rule coverage.
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 2/75 engines detected the archive.
- engines.tier1Malicious=0 and 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- externalIntel.malwareBazaar.hit=false and externalIntel.circl.hit=false.
- Runtime evidence maps activity to T1055 process injection.
- Runtime evidence maps activity to T1562.001 impairment of defenses.
- Two extracted children remain unclassified.
- NANO-Antivirus reported the Fisaez family.
- Skyhigh reported an Artemis PUP label.
- The ZIP is encrypted and contains an executable.
Keep endpoint protection enabled and verify the archive against Microsoft's official security-testing materials. If its source cannot be confirmed, quarantine it; otherwise, use it only in an isolated lab.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 3 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
- 10MITRE ATT&CK techniques
- 4spawned processes
- 3network contacts
- 4filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
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: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
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
MDECloudProtectionDemoTest (1).zip
c7d76d9791767ce743eb4f932d0a5c581db0b903398fdf8b8a1563eec9fcfcd9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\SysWOW64\unarchiver.exe" "C:\Users\user\Desktop\MDECloudProtectionDemoTest.zip"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
oztxpzrt.czr
C:\Users\user\AppData\Local\Temp\oztxpzrt.czr
04Isolated runtime analysis - Written fileObserved
670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04
C:\Users\user\AppData\Local\Temp\oztxpzrt.czr\670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
edge.ds-c7110-microsoft.global.dns.qwilted-cds.cqloud.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
default.qdr.p1.ds-c7110-microsoft.global.dns.qwilted-cds.cqloud.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 and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- edge.ds-c7110-microsoft.global.dns.qwilted-cds.cqloud.com
- default.qdr.p1.ds-c7110-microsoft.global.dns.qwilted-cds.cqloud.com
- 173.194.195.94
- C:\Users\user\AppData\Local\Temp\oztxpzrt.czr
- C:\Users\user\AppData\Local\Temp\oztxpzrt.czr\670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04
- C:\Users\user\AppData\Local\Temp\unarchiver.log
- \Device\ConDrv\\Connect
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 670b00e90a7c9eb7ac66…ac4c04Never scannednever seen before
- a92a46b95813e3d8bdca…4394aaNever 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
- 2 / 75engines flagged
- 32sources 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
2 of 75 antivirus engines flagged the file, including NANO-Antivirus and Skyhigh.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 52 times from 32 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: MDECloudProtectionDemoTest (1).zip — c7d76d9791767ce743eb4f932d0a5c581db0b903398fdf8b8a1563eec9fcfcd9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\SysWOW64\unarchiver.exe" "C:\Users\user\Desktop\MDECloudProtectionDemoTest.zip"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: oztxpzrt.czr — C:\Users\user\AppData\Local\Temp\oztxpzrt.czr
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04 — C:\Users\user\AppData\Local\Temp\oztxpzrt.czr\670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: edge.ds-c7110-microsoft.global.dns.qwilted-cds.cqloud.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: default.qdr.p1.ds-c7110-microsoft.global.dns.qwilted-cds.cqloud.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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:\Users\<USER>\AppData\Local\Temp\670b00e90a7c9eb7ac6674441551e7764a8364c26e44dcc92474a9abcfac4c04.exe"
2 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
- MDECloudProtectionDemoTest (1).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 49.3 KB
- Last analyzed
- Sep 28, 2026, 3:35 AM UTC
c7d76d9791767ce743eb4f932d0a5c581db0b903398fdf8b8a1563eec9fcfcd9Safety & 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 MDECloudProtectionDemoTest (1).zip safe, or is it malware?
What is MDECloudProtectionDemoTest (1).zip?
How many antivirus engines detected MDECloudProtectionDemoTest (1).zip?
What should I do if I already opened or extracted MDECloudProtectionDemoTest (1).zip?
How do I remove MDECloudProtectionDemoTest (1).zip?
What is the SHA-256 hash of MDECloudProtectionDemoTest (1).zip?
How up to date is this analysis of MDECloudProtectionDemoTest (1).zip?
Community
Member reviews and reports for this exact file hash.