File verdict·Decided by the MT AI Engine
Our call

Suspicious

Unsigned JavaScript exhibiting process injection and credential-dumping techniques; tier-1 engines silent but heuristics flagged malware-like behaviour.

Trust score58Caution
MT AI confidence · 62%
scripts.js
17.0 KB
4f4d54e702245a2c414da140c716
Antivirus engines
0 of 76 flagged
Code signing
Unsigned
Age
First seen 4mo ago
MT AI Engine · our arbiter

The verdict, reasoned out.

Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.

62%Confidence
Moderate
Reasoning

The file presents a mixed-signal profile. On one hand, the triggered heuristics (MalwareTips.Synth.ProcessInjection and MalwareTips.Synth.CredentialDumper) name specific offensive techniques — process injection via CreateRemoteThread/APC and LSASS memory access — that are hallmarks of credential-theft malware like Mimikatz. The MITRE technique set (T1055, T1082, T1071, T1027, T1064) aligns with post-exploitation activity. On the other hand, the complete silence from 17 tier-1 engines (Microsoft Defender, Kaspersky, ESET, BitDefender, Fortinet, Avast, Avira, Emsisoft, GData, Ikarus, DrWeb, F-Secure, and others) is a strong counter-signal — genuine malware families are typically caught by at least one tier-1 vendor. The sandbox did not return a malicious verdict despite observing the suspicious behaviour, and no external-intel sources (CIRCL, YARAify, MalwareBazaar) have flagged the sample. The file is unsigned, generic-named, and 130 days old with only 2 submissions, which does not fit the profile of an active malware campaign. The most likely explanation is that the heuristics detected legitimate-but-suspicious script activity (e.g., a system-administration or penetration-testing script) rather than weaponized malware.

Key signals · 5

Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.

  1. tier1Malicious=0; 17 tier-1 engines (Avast, BitDefender, ESET, Kaspersky, Microsoft, Fortinet, Ikarus, Emsisoft, GData, Avira, DrWeb, F-Secure) all reported undetected

  2. triggeredHeuristics: MalwareTips.Synth.ProcessInjection (T1055) + MalwareTips.Synth.CredentialDumper (LSASS targeting) both fired with high/medium severity

  3. behaviour.mitreTechniques=[T1027, T1055, T1064, T1071, T1082]; offensiveTechniques=[T1055] — process injection is offensive-only technique

  4. No external-intel hits (CIRCL, YARAify, MalwareBazaar all negative); no similar-hash RAG entries; no malicious sandbox verdict recorded

  5. Unsigned JavaScript; generic filename; no brand mismatch; prevalence medium (2 submitters, 130 days) — not rare-new

Points in its favour
  • All 17 tier-1 antivirus engines reported undetected — strong signal against malware classification
  • No external-intel corroboration (CIRCL, YARAify, MalwareBazaar all negative) — not in researcher-curated threat databases
  • No malicious sandbox verdict recorded — sandbox did not classify behaviour as conclusively malicious
  • File age 130 days with only 2 submissions — low prevalence inconsistent with active malware campaign
Points against
  • Process injection (T1055) heuristic triggered — suggests attempt to hide code in legitimate process
  • LSASS access detected — consistent with credential-dumping malware
  • Unsigned script — no publisher verification or code integrity
  • Multiple system processes spawned — could indicate privilege escalation or lateral movement
  • Obfuscation techniques detected (T1027) — suggests intent to evade detection
What to do

Treat this file as suspicious pending manual code review. The heuristic alerts warrant caution, but the tier-1 engine silence and lack of external-intel corroboration suggest a false positive or benign-but-suspicious script. Do not execute on production systems without understanding its source and purpose; if it is a legitimate tool, whitelist it after verification.

Runtime behaviour

What this file did when executed

This file was detonated in 1 sandbox and its runtime behaviour was observed.

MITRE ATT&CK
5

Adversary techniques mapped to the MITRE ATT&CK framework.

T1027T1055T1064T1071T1082
Spawned processes
8
$(unnamed)
"C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\scripts.js"
$(unnamed)
C:\Windows\system32\services.exe
$(unnamed)
C:\Windows\System32\svchost.exe -k NetworkService -p
$(unnamed)
C:\Windows\system32\svchost.exe -k UnistackSvcGroup
$(unnamed)
C:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc
$(unnamed)
C:\Windows\system32\lsass.exe
$(unnamed)
C:\Windows\system32\svchost.exe -k LocalService -s W32Time
$(unnamed)
C:\Windows\System32\wscript.exe C:\Windows\System32\WScript.exe "C:\Users\user\Desktop\scripts.js"
Filesystem & mutexes
1
Files written1
  • C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
No researcher-database hits
External threat-intel sources were not collected for this scan.
Signature matches

YARA + heuristic rules that fired

A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.

2 synthesis
MITRE ATT&CK profile
Defense evasion× 1Cred access× 1
MalwareTips synthesis rules
Our heuristics on VT data + sandbox behaviour
  • ProcessInjectionhigh

    MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.

    Evidence
    C:\Windows\System32\svchost.exe -k NetworkService -p
  • CredentialDumpermedium

    Sandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.

    Evidence
    C:\Windows\system32\lsass.exe
Antivirus engine breakdown

0 detections across 76 engines

0 malicious0 suspicious76 clean
Tier-117 engines
0flag
Top commercial AVs (low FP rate)
Tier-238 engines
0flag
Mainstream engines with mixed FP rates
Low-trust21 engines
0flag
Heuristic / generic-AI engines (high FP rate)
All 76 engines report this file as clean.
Hash 4f4d54e70224… cross-referenced against 76 AV engines via our AV network.
Prevalence

How often this file shows up in the wild

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
2
Very few people have ever uploaded this — rare.
Total submissions
2
Includes repeat uploads by the same source.
First seen by VT
4mo ago
Feb 16, 2026
Prevalence quadrant
Rare · New
Targeted malware lives here
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Trusted legitimate binaries
File identity

Forensic fingerprint

File biography
First seen (VT)
2/16/2026, 10:26:45 AM
First seen (MalwareBazaar)
Last analysis (VT)
2/16/2026, 10:26:45 AM
Scanned here
6/26/2026, 4:15:35 PM
File name
scripts.js
Size
17.0 KB
MIME type
(unknown)
Detected type
JavaScript
SHA-256
4f4d54e702245a2c411f04125658a4d6b8aa8c553bd7c3bfd978214da140c716
MD5
0f1c7eae2cdae9ad9dd34fb0faee38ca
SHA-1
20028debf3175f129a0cbc490e9464d63d896fc1
First seen (VT)
2/16/2026, 10:26:45 AM
Last analysis (VT)
2/16/2026, 10:26:45 AM
First scan (MalwareTips)
6/26/2026, 4:15:35 PM
Last scan (MalwareTips)
6/26/2026, 4:15:35 PM
Behavior tags
javascriptlong-sleeps
Community classification

Reviews & malware reports(0)

Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.

Loading…
Loading reports…
Files are processed in a streaming pass-through — MalwareTips never stores the binary on its servers. Only the scan result (hash, detections, verdict) is retained so the next person who scans the same file gets an instant answer. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.