Is q-sniper.user.js safe?
No antivirus detections, yet sandbox flagged process-injection and LSASS activity with incomplete host-reputation coverage.
Zero of 76 engines flagged the JavaScript file. Sandbox evidence shows T1055 and LSASS access, but no malicious verdict or known-bad host correlation exists. Host-reputation cross-check was not completed, leaving the verdict unknown.
c45ebcb331a788c61d…d13f259c377e45Recommended 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.
Zero of 76 engines flagged the JavaScript file. Sandbox evidence shows T1055 and LSASS access, but no malicious verdict or known-bad host correlation exists. Host-reputation cross-check was not completed, leaving the verdict unknown.
The file is a 2.4 KB JavaScript with medium prevalence and no engine detections. Sandbox recorded process-injection and LSASS activity, yet returned no malicious verdict. Because contactedHosts is null, the single direct-IP contact cannot be assessed. External intelligence sources are silent. Low coverage and missing host reputation data keep the verdict at unknown.
What We Detected
76 engines scanned the file; none returned a malicious or suspicious result. Sandbox execution recorded MITRE T1055 (Process Injection) and LSASS access, but produced no malicious verdict. One external IP was contacted; host reputation data is unavailable.
Threat Behavior
The script triggered synthetic heuristics for process injection and credential-dumping patterns, yet no dropped malicious children or persistence indicators were observed. External-intel sources (CIRCL, MalwareBazaar, YARAify) returned zero hits.
What To Do Now
Do not execute the script until a complete host-reputation check is available. Keep endpoint protection enabled and avoid running untrusted JavaScript files that interact with system processes.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access and direct-IP contact, but no malicious sandbox verdict or known-bad host correlation.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero engine detections across 76 scanners
- No external-intel malicious hits
- Sandbox observed LSASS access
- Direct-IP contact without domain
- contactedHosts reputation check incomplete
Treat the file as unknown until host-reputation coverage is completed; do not run it in production environments.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 4MITRE ATT&CK techniques
- 8spawned processes
- 1network 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
q-sniper.user.js
c45ebcb331a788c61dcdea285e34a9be62e0cd024594e0d2d8d13f259c377e45
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\q-sniper.user.js"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
05Isolated runtime analysis
5 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.
- 162.159.36.2
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 0 / 76engines flagged
- 7sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 76 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 7 times from 7 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: q-sniper.user.js — c45ebcb331a788c61dcdea285e34a9be62e0cd024594e0d2d8d13f259c377e45
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\q-sniper.user.js"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
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
- q-sniper.user.js
- Format
- JavaScript
- Code signing
- Not applicable to this file type
- Size
- 2.4 KB
- Last analyzed
- Aug 19, 2026, 11:19 PM UTC
c45ebcb331a788c61dcdea285e34a9be62e0cd024594e0d2d8d13f259c377e45Safety & 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 q-sniper.user.js safe? What is it?
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?
How up to date is this analysis of q-sniper.user.js?
Community
Member reviews and reports for this exact file hash.