Is zz_2in1_Unlocker_0.12.0.rpy safe?
No antivirus engine flagged the Python script and sandbox behaviour was benign.
Zero detections across 75 engines, one sandbox run showed only system-info discovery, and no external-intel hits. The single heuristic on direct-IP traffic is inconclusive without host reputation data.
52cae47ec10b4bf15a…a3c8280cb892deRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
Zero detections across 75 engines, one sandbox run showed only system-info discovery, and no external-intel hits. The single heuristic on direct-IP traffic is inconclusive without host reputation data.
The file is a 14-day-old Python script with medium prevalence. All 75 reporting engines returned clean, including 16 tier-1 engines. Sandbox execution produced only ambient system-information calls and no malicious verdict. The triggered heuristic notes direct-IP traffic but explicitly states it is not decisive without further correlation. No external-intel sources corroborate malice.
What We Detected
75 engines scanned the 20 kB Python file; none returned a malicious or suspicious label. Sandbox execution logged only T1082 system-information discovery and wrote to pseudo-terminals, typical of normal script execution.
Threat Behavior
No offensive MITRE techniques, no dropped children, no persistence indicators. Two direct IP addresses were contacted, but the heuristic rule itself cautions against treating this as C2 without host-reputation confirmation.
What To Do Now
The file can be executed in a controlled environment if needed; keep endpoint protection enabled. If the script is required for legitimate work, verify its source and review the code before broader deployment.
Where this verdict could be wrong1 caveat
- contactedHosts is null — no complete host-reputation result available for the two observed IPs.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- zero malicious detections across 75 engines
- sandbox returned no malicious verdict
- medium prevalence with consistent submissions
- contactedHosts cross-check incomplete
Treat the script as safe for controlled testing; monitor any outbound connections and keep security software active.
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
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 1MITRE ATT&CK techniques
- 5spawned processes
- 2network contacts
- 4filesystem & mutex artifacts
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
zz_2in1_Unlocker_0.12.0.rpy
52cae47ec10b4bf15a899032f95ea91163eac9ea1d00966485a3c8280cb892de
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
xterm -hold -e /usr/bin/python /tmp/file.py
02Isolated runtime analysis - ProcessObserved
Observed process
/usr/bin/python /tmp/file.py
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
tty
/dev/tty
04Isolated runtime analysis - Written fileObserved
ptmx
/dev/ptmx
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
185.125.188.58
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
185.125.188.54
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.125.188.58
- 185.125.188.54
- /dev/tty
- /dev/ptmx
- /dev/pts/0
- \Device\ConDrv\\Connect
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
- 8sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 8 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: zz_2in1_Unlocker_0.12.0.rpy — 52cae47ec10b4bf15a899032f95ea91163eac9ea1d00966485a3c8280cb892de
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — xterm -hold -e /usr/bin/python /tmp/file.py
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /usr/bin/python /tmp/file.py
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: tty — /dev/tty
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ptmx — /dev/ptmx
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 185.125.188.58 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 185.125.188.54 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidence185.125.188.58 · 185.125.188.54
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
- zz_2in1_Unlocker_0.12.0.rpy
- Format
- Python
- Code signing
- Not applicable to this file type
- Size
- 20.1 KB
- Last analyzed
- Aug 23, 2026, 4:34 AM UTC
52cae47ec10b4bf15a899032f95ea91163eac9ea1d00966485a3c8280cb892deSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open it only when its sender or download source is one you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is zz_2in1_Unlocker_0.12.0.rpy safe?
What is zz_2in1_Unlocker_0.12.0.rpy?
How many antivirus engines detected zz_2in1_Unlocker_0.12.0.rpy?
What is the SHA-256 hash of zz_2in1_Unlocker_0.12.0.rpy?
Is it safe to open zz_2in1_Unlocker_0.12.0.rpy?
How up to date is this analysis of zz_2in1_Unlocker_0.12.0.rpy?
Community
Member reviews and reports for this exact file hash.