Is content.js safe?
No antivirus engine identified malware, but obfuscation and a sandbox mapping to process injection warrant caution until the script’s origin and code are verified.
All 75 antivirus engines avoided flagging this JavaScript, and the sandbox issued no malware verdict. However, the file is tagged as obfuscated and the runtime record maps activity to process injection, with an additional LSASS-related heuristic, so it should not be trusted without source review.
14c0cdd117c48edfe3…2f7a3a45901c6cRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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 antivirus engines avoided flagging this JavaScript, and the sandbox issued no malware verdict. However, the file is tagged as obfuscated and the runtime record maps activity to process injection, with an additional LSASS-related heuristic, so it should not be trusted without source review.
The strongest reassuring evidence is that 0 of 75 engines flagged the sample, including no tier-1 detections. One completed sandbox run did not issue a malware verdict or record network contacts. However, the runtime mapping includes T1055, and an LSASS-related heuristic raises concern about possible credential-access behavior, though its saved evidence only identifies the LSASS process and does not prove memory access. Obfuscation and long-sleep tags also complicate static inspection and can be associated with evasion. No malicious child, known family, or external research match corroborates those concerns, leaving the evidence mixed rather than decisive.
What We Detected
None of 75 antivirus engines flagged the JavaScript, including all 17 tier-1 engines represented in the results. External checks produced no MalwareBazaar match, CIRCL hit, or YARAify rule match. Code signing does not apply to this file type.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055, which can indicate process injection. A credential-dumper heuristic also fired because LSASS appeared in the process evidence, but the saved data does not document an actual LSASS-memory read or a malicious sandbox conclusion. The sample is tagged as obfuscated and using long sleeps; one written child was inspected but remains unknown. The run recorded no contacted domains, IP addresses, or URLs, while no separate contacted-host reputation result is available.
What To Do Now
Do not execute the script outside an isolated environment until its source and unobfuscated code are verified. If it arrived unexpectedly, remove or quarantine it and keep endpoint protection enabled; if it belongs to a browser extension or trusted project, compare its hash and contents with the publisher’s official release.
Where this verdict could be wrong4 caveats
- The file carries the tags obfuscated and long-sleeps, which can indicate evasion even though no engine detected a threat.
- T1055 and the LSASS-related heuristic are meaningful behavioural concerns that prevent treating the engine result as conclusive.
- droppedChildren.rollup reports one unknown child, so the written file has not been affirmatively cleared.
- contactedHosts=null means no separate host-reputation cross-check is available, although this run recorded no network contacts.
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 of 75 antivirus engines reported a detection.
- No tier-1 engine reported malware.
- The completed sandbox produced no malicious verdict.
- No malicious dropped child was established.
- No MalwareBazaar, CIRCL, or YARAify match was found.
- Runtime evidence includes MITRE T1055.
- An LSASS-related credential-dumper heuristic fired.
- The file is tagged as obfuscated and using long sleeps.
- The single written child remains unknown.
- No complete contacted-host reputation result is available.
Keep the script quarantined until its provenance and unobfuscated contents are verified against an official source. Do not disable endpoint protection to run or install it.
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
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 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
- 12MITRE ATT&CK techniques
- 8spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
content.js
14c0cdd117c48edfe3bf4af7a4efd9b1901d64be0192f9bc072f7a3a45901c6c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\background.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 - Dropped fileDerived
792eade5589d57e8cbc781763d06316212c37d438d498348c590fd4e73b0fdab
No child-file verdict was available.
05Dropped-file analysis - +1 more recorded observation in Analyst mode
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.
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\W32Time\Config\LastKnownGoodTime
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 792eade5589d57e8cbc7…b0fdabNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 11sources 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 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 16 times from 11 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: content.js — 14c0cdd117c48edfe3bf4af7a4efd9b1901d64be0192f9bc072f7a3a45901c6c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\background.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
Dropped file: 792eade5589d57e8cbc781763d06316212c37d438d498348c590fd4e73b0fdab — No child-file verdict was available.
ProvenanceDerivedSourceDropped-file 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.exe
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
- content.js
- Format
- JavaScript
- Code signing
- Not applicable to this file type
- Size
- 3.8 KB
- Last analyzed
- Oct 3, 2026, 12:27 PM UTC
14c0cdd117c48edfe3bf4af7a4efd9b1901d64be0192f9bc072f7a3a45901c6cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is content.js safe, or is it malware?
What is content.js?
How many antivirus engines detected content.js?
I already downloaded and ran content.js — what should I do?
How do I remove content.js?
What is the SHA-256 hash of content.js?
How up to date is this analysis of content.js?
Community
Member reviews and reports for this exact file hash.