Is RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip safe?
No engine detected a threat, and the completed sandbox run showed archive handling without offensive techniques, persistence, dropped payloads, or a malicious runtime assessment.
All 76 antivirus engines were free of detections, including 18 high-trust engines. One sandbox run only recorded archive-opening and listing activity, with no offensive techniques, persistence, dropped payloads, or malicious runtime assessment; limited prevalence and incomplete external checks warrant ordinary caution.
5e824dfa1b26866750…0270b835d847ddRecommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted 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.
All 76 antivirus engines were free of detections, including 18 high-trust engines. One sandbox run only recorded archive-opening and listing activity, with no offensive techniques, persistence, dropped payloads, or malicious runtime assessment; limited prevalence and incomplete external checks warrant ordinary caution.
The ZIP received no malicious or suspicious detections from 76 engines, with all 18 participating tier-1 engines reporting no detection. One completed sandbox run showed the archive being opened and listed by standard utilities rather than executing an embedded payload. It recorded no offensive-only techniques, persistence indicators, dropped hashes, network contacts, or malicious sandbox assessment. The archive is 616 days old, but it has only one recorded submission, so its reputation history is limited. Host-reputation checking was not completed or saved, and two external-intelligence sources were skipped, but there are no affirmative threat signals in the available evidence.
What We Detected
No malicious or suspicious detections appeared among 76 antivirus engines. All 18 reporting tier-1 engines, including Kaspersky, BitDefender, ESET-NOD32, Fortinet, and Avast, returned no detection.
Threat Behavior
One sandbox run opened and listed the ZIP with standard archive utilities. It recorded no offensive-only techniques, persistence indicators, dropped file hashes, network contacts, or malicious runtime assessment. A complete contacted-host reputation cross-check was not available, and MalwareBazaar and YARAify coverage was skipped.
What To Do Now
The available evidence does not indicate an active threat. Keep endpoint protection enabled, extract the archive cautiously, and scan any executable or script found inside before opening it.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_old reflects only one source and one submission, so the file has little reputation history.
- contactedHosts=null means no completed host-reputation cross-check was saved.
- externalIntel.availability shows YARAify and MalwareBazaar were skipped, limiting independent intelligence 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.
- 0/76 antivirus engines reported malicious or suspicious results.
- 18 tier-1 engines reported no detection.
- One completed sandbox run produced no malicious verdict.
- No offensive techniques, persistence indicators, or dropped payload hashes were recorded.
- No brand mismatch or adversarial-input flag was detected.
- Only one source and one submission are recorded for this hash.
- The contacted-host reputation cross-check was not completed or saved.
- MalwareBazaar and YARAify intelligence checks were skipped.
The archive can be handled with normal caution. Keep endpoint protection enabled and rescan any extracted executable, script, or shortcut before opening it.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 2MITRE ATT&CK techniques
- 6spawned processes
- 0network contacts
- 1filesystem & 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
RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip
5e824dfa1b26866750224e267f5b6019007850f4a0f33600490270b835d847dd
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
/usr/bin/exo-open exo-open /tmp/RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip
02Isolated runtime analysis - ProcessObserved
Observed process
/usr/bin/dbus-launch dbus-launch --autolaunch=a39eb3ed78b7401fb6809ed0c562a5b1 --binary-syntax --close-stderr
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
user
/root/.cache/dconf/user
04Isolated runtime analysis
4 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.
- /root/.cache/dconf/user
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 76engines 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
0 of 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip — 5e824dfa1b26866750224e267f5b6019007850f4a0f33600490270b835d847dd
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — /usr/bin/exo-open exo-open /tmp/RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — /usr/bin/dbus-launch dbus-launch --autolaunch=a39eb3ed78b7401fb6809ed0c562a5b1 --binary-syntax --close-stderr
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: user — /root/.cache/dconf/user
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 76 engines flagged this file
View all 76 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 19.0 MB
- Last analyzed
- Sep 16, 2026, 10:18 AM UTC
5e824dfa1b26866750224e267f5b6019007850f4a0f33600490270b835d847ddSafety & 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 or extract it only when its sender or download source has been independently verified.
- 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 RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip safe?
What is RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip?
How many antivirus engines detected RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip?
What is the SHA-256 hash of RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip?
Is it safe to open or extract RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip?
How up to date is this analysis of RVN.Mushoku.Tensei.-.Volumen.02.SC.CF.zip?
Community
Member reviews and reports for this exact file hash.