File scan report
Verdict Safe
Is q- sniper. user. js safe? Yes, no threats found.
This small browser user script was not flagged by any of the 76 engines, and the sandbox runs recorded no high-risk behaviour.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The script appears clean. Install it only through a browser userscript manager from a source you trust, and review what pages it is allowed to run on.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 61 flagged
- Flagged 0
- No detection 61
- No result 15
- Code signing Not applicable
- Test run Completed
- First seen 6mo ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 61 antivirus engines that checked it flagged this 2.4 KB user script, including all 18 major antivirus engines that returned a result. The sandbox runs showed no confirmed injection, no persistence and no network activity of its own. The file has circulated for about six months among several submitters without picking up detections.
Engine coverage is adequate, with 61 engines reporting, and none of the 61 antivirus engines that checked it flagged the file. The sandbox runs mapped a process-injection technique but recorded no injected process. That mapping appears on many clean files and is not evidence here. The only network contact was the analysis machine's own background traffic. The file is a small userscript meant for a browser extension, and it has been seen for 187 days without any detections.
What We Detected
None of the 61 antivirus engines that checked it flagged this 2,432-byte JavaScript user script. All 18 major antivirus engines that returned a result reported it clean.
Threat Behavior
The sandbox runs opened the script with the Windows script host. They recorded no persistence, no registry changes, no dropped executables and no network contact beyond the analysis machine's background traffic. Our own static analysis was not run on these bytes.
What To Do Now
User scripts are meant to run inside a browser userscript manager, not by double-clicking them in Windows. Install it only from a source you trust, and keep your antivirus enabled.
Where this verdict could be wrong1 caveat
- Our own static analysis did not run on these bytes and no reference-database result is available, so the script's contents were not independently reviewed beyond the engine scans.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 61 antivirus engines that checked it flagged the file, including every major antivirus engine that returned a result
- No high-risk techniques were confirmed in the sandbox runs
- No network activity of its own beyond the analysis machine's background traffic
- Seen for about six months by several submitters without any detections
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 4sandbox rule tags
- 2spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
Includes 4 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 61 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Aug 19, 2026, 11:19 PM UTC
- SHA-256
c45ebcb331a788c61dcdea285e34a9be62e0cd024594e0d2d8d13f259c377e45- SHA-1
ef532d6d3e5beeadb6b83b0341f1ee4c32f10ac4- MD5
93c3b6fbef4480ab42492375a44c509e
About this file
q-sniper.user.js is a JavaScript file of 2.4 kB.
- Type and size
- JavaScript · 2.4 kB
- Signer
- Not applicable
- First seen
- Apr 15, 2026On VirusTotal.
- Submitted by
- 7 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned Updated
Verdict history
- Not fully confirmed
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (76), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is q-sniper.user.js safe?
What is q-sniper.user.js?
How many antivirus engines detected q-sniper.user.js?
What is the SHA-256 hash of q-sniper.user.js?
Is it safe to run q-sniper.user.js?
How up to date is this analysis of q-sniper.user.js?
Community
Member reviews and reports for this exact file hash.