Is Proxy.js safe?
A brand-new JavaScript file with zero detections but no sandbox or host-reputation data.
All 75 engines returned clean, yet the file is only hours old and has never been sandboxed. Without runtime or network evidence, the verdict stays unknown.
a091a4e7ecd6719e1b…c63d8447386ab9Recommended next actions
Before running
Treat the file as unverified and avoid running it until more evidence is available.
If you already ran it
Run a full device scan. If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source.
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 75 engines returned clean, yet the file is only hours old and has never been sandboxed. Without runtime or network evidence, the verdict stays unknown.
Zero malicious detections across 75 reporting engines, including 16 tier-1 engines, is a strong static signal. However, the file is a rare_new JavaScript sample submitted for the first time today, so prevalence data is minimal. No sandbox execution, no contacted-host reputation check, and no external-intel hits leave a coverage gap that prevents a confident clean or malicious call.
What We Detected
61 of 75 engines scanned the 5 kB JavaScript file; none flagged it malicious or suspicious. No YARA, CIRCL or MalwareBazaar rules matched.
Threat Behavior
No sandbox trace or network activity is available. The file has not been executed in our environment, and contacted-host reputation data is missing.
What To Do Now
Run the script only in an isolated environment or wait for additional submissions and sandbox results before trusting it in production.
- 0/75 engines flagged malicious
- no external intelligence hits
- rare_new submission with single source
- no sandbox or network reputation data
Treat the file as untrusted until sandbox or additional engine coverage becomes available.
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
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
No completed runtime observation is available for this file.
Verdict inputView chapterProvenanceDerivedSourceRuntime coverageObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- Proxy.js
- Format
- JavaScript
- Code signing
- Not applicable to this file type
- Size
- 5.1 KB
- Last analyzed
- Aug 15, 2026, 1:35 PM UTC
a091a4e7ecd6719e1b3f608b788ecf538e56d3509496f6ed14c63d8447386ab9Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
There isn't enough information to give this file a clear rating.
- Recovery step 01
Be cautious — an unknown rating is not the same as a clean bill of health.
- Recovery step 02
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 03
When in doubt, don't run it — or scan it again later once it's more widely seen.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Proxy.js safe? What is it?
What is Proxy.js?
How many antivirus engines detected Proxy.js?
What is the SHA-256 hash of Proxy.js?
How up to date is this analysis of Proxy.js?
Community
Member reviews and reports for this exact file hash.
