Is beam-ng.drive-0.28.2_archive.torrent safe?
No antivirus engine detected a threat, and the established submission history lacks corroborating intelligence, although the torrent-name and JavaScript-type mismatch merits caution.
None of 75 antivirus engines flagged this file, including all 18 reporting tier-1 engines, and independent intelligence produced no threat matches. Its established submission history supports a benign interpretation, but the apparent mismatch between a torrent-style filename and JavaScript classification should be verified before opening.
2e0dad67fe064c8953…f1f644f18c9fcfRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
None of 75 antivirus engines flagged this file, including all 18 reporting tier-1 engines, and independent intelligence produced no threat matches. Its established submission history supports a benign interpretation, but the apparent mismatch between a torrent-style filename and JavaScript classification should be verified before opening.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with no high-trust engine identifying malware. No matching malware family, research rule, malicious child, or other corroborating threat indicator is present. The file has been submitted 35 times by 32 sources and is hundreds of days old, reducing concern that it is an entirely new sample. However, no sandbox execution was completed, and no complete contacted-host reputation result is available. The unusual discrepancy between the .torrent-style name and JavaScript classification is therefore the main residual concern.
What We Detected
None of 75 antivirus engines flagged the sample, and tier1Malicious=0. Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast were among the engines reporting no detection. Malware-family intelligence and research-rule checks also returned no matches.
Threat Behavior
No completed sandbox observation is available because behaviour=null, so runtime actions were not observed. contactedHosts=null also means no complete host-reputation cross-check is available. The main anomaly is that the filename resembles a torrent archive while file.fileType identifies JavaScript.
What To Do Now
Confirm that the file is actually a torrent metadata file before opening it. If it contains JavaScript or launches a script interpreter, do not execute it; obtain a replacement from the expected official source and keep endpoint protection enabled.
Where this verdict could be wrong3 caveats
- behaviour=null, so the file was not dynamically observed and potentially harmful script activity cannot be excluded through runtime evidence.
- contactedHosts=null, meaning no complete reputation result is available for any hosts the file might contact when opened.
- The .torrent filename conflicts with file.fileType=JavaScript, an unusual mismatch that warrants confirming the file's true format before execution.
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 malicious or suspicious result.
- All 18 reporting tier-1 engines produced no detection.
- No MalwareBazaar, CIRCL, or YARAify match was found.
- The hash has 35 submissions from 32 unique sources.
- No malicious dropped child or brand mismatch is reported.
- The .torrent-style filename conflicts with file.fileType=JavaScript.
- No completed sandbox runtime observation is available.
- No complete contacted-host reputation cross-check is available.
Verify the true file format and source before opening it because a torrent-named JavaScript file is unusual. Keep endpoint protection enabled and avoid execution if the file invokes a script interpreter.
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
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
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 / 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
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 35 times from 32 sources.
ProvenanceDerivedSourceSaved report factsObserved 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- beam-ng.drive-0.28.2_archive.torrent
- Format
- JavaScript
- Code signing
- Not applicable to this file type
- Size
- 107.0 KB
- Last analyzed
- Sep 18, 2026, 7:00 PM UTC
2e0dad67fe064c895334f4af923d73691374ffdfe4403fe655f1f644f18c9fcfSafety & 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
Run it only when it came from the developer's official site or another source 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 beam-ng.drive-0.28.2_archive.torrent safe?
What is beam-ng.drive-0.28.2_archive.torrent?
How many antivirus engines detected beam-ng.drive-0.28.2_archive.torrent?
What is the SHA-256 hash of beam-ng.drive-0.28.2_archive.torrent?
Is it safe to run beam-ng.drive-0.28.2_archive.torrent?
How up to date is this analysis of beam-ng.drive-0.28.2_archive.torrent?
Community
Member reviews and reports for this exact file hash.