Is sv_pureLevelBypass.map safe?
No engine detections or external-intelligence matches were found, and the two-year-old JavaScript file has moderate, established prevalence across independent submissions.
None of 76 antivirus engines flagged this JavaScript file, including all 18 participating tier-1 engines. Its age and submission history further reduce concern, although no completed runtime observation or contacted-host reputation assessment is available.
aa3caa465ae9b21a51…bcf2df799667adRecommended 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 76 antivirus engines flagged this JavaScript file, including all 18 participating tier-1 engines. Its age and submission history further reduce concern, although no completed runtime observation or contacted-host reputation assessment is available.
The strongest evidence is the complete absence of detections across 76 antivirus engines, with all 18 participating tier-1 engines reporting no detection. The sample has been known for 844 days and appeared through 47 independent sources across 50 submissions, which is inconsistent with a newly emerging payload. CIRCL, MalwareBazaar, and YARAify supplied no malicious corroboration. Code signing is not applicable to this JavaScript file and therefore carries no negative weight. No runtime observation was completed, and contacted-host reputation was not assessed, so those areas remain unverified rather than clean.
What We Detected
None of 76 antivirus engines flagged the file, and all 18 participating tier-1 engines—including Microsoft, Kaspersky, BitDefender, and ESET-NOD32—reported no detection. No matching malicious family, YARA rule, or curated threat-intelligence record was found.
Threat Behavior
No completed sandbox observation is available, so execution behavior cannot be characterized. A complete contacted-host reputation result is also unavailable; this does not indicate benign network activity, only missing coverage.
What To Do Now
The available static and reputation evidence does not indicate a threat. Keep endpoint protection enabled, and obtain the file from its expected source before opening or using it in a development workflow.
Where this verdict could be wrong2 caveats
- behaviour=null, so the file was not validated through completed runtime observation.
- contactedHosts=null, so no complete reputation assessment exists for any hosts the script might contact when executed.
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 a detection.
- All 18 participating tier-1 engines reported no detection.
- Observed for 844 days across 47 independent sources and 50 submissions.
- No CIRCL, MalwareBazaar, or YARAify match was found.
- No brand mismatch or adversarial-input flag was detected.
- No completed runtime observation is available.
- No complete contacted-host reputation assessment is available.
Normal use is reasonable if the file came from the expected source. Keep endpoint protection enabled and rescan if the file changes or originates from an untrusted download.
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
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 / 76engines flagged
- 47sources 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
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 50 times from 47 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 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- sv_pureLevelBypass.map
- Format
- JavaScript
- Code signing
- Not applicable to this file type
- Size
- 136.1 KB
- Last analyzed
- Sep 29, 2026, 5:02 PM UTC
aa3caa465ae9b21a51e5a9def659115553cbae5bb5b65a972bbcf2df799667adSafety & 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 sv_pureLevelBypass.map safe?
What is sv_pureLevelBypass.map?
How many antivirus engines detected sv_pureLevelBypass.map?
What is the SHA-256 hash of sv_pureLevelBypass.map?
Is it safe to run sv_pureLevelBypass.map?
How up to date is this analysis of sv_pureLevelBypass.map?
Community
Member reviews and reports for this exact file hash.