File scan report
Verdict Safe
Is 4ENEVERSEENBEFOREBYRAIN. jar safe? Yes, no threats found.
Zero detections across 75 engines and no malicious files it created despite three MITRE techniques observed.
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the project's own website.
Keep your security software and system 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 64 flagged
- Flagged 0
- No detection 64
- No result 11
- Code signing Not applicable
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
1 point against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
No antivirus engine flagged the JAR.
The complete absence of detections from 75 engines, including 17 major antivirus engines, outweighs the three MITRE techniques recorded in a single sandbox run. Those techniques are common in dual-use or research tooling and were not corroborated by any malicious sandbox verdict or dropped malicious child. Medium prevalence over nearly two months and zero external-intel hits further support a benign classification.
What We Detected
75 engines scanned the 487 kB JAR; none returned a malicious or suspicious result. One sandbox execution captured MITRE techniques T1055 (process injection), T1543.002 (new service) and T1562.001 (defence-evasion), but the sandbox itself did not classify the sample as malicious.
Threat Behavior
The observed techniques can appear in legitimate Java utilities, debuggers or research tools. No persistence registry keys, program markers or malicious files it created were found. no complete contacted-host reputation result was available.
What To Do Now
The file can be executed in an isolated test environment if its origin is trusted. Keep security software enabled; no disabling of security software is warranted.
Where this verdict could be wrong1 caveat
- contactedHosts is null — no complete host-reputation cross-check available.
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 detections from 75 engines
- No malicious files it created
- Medium prevalence over 58 days
- Three offensive MITRE techniques observed in sandbox
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- 16sandbox rule tags
- 3spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
16MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1055· Process injection
- T1059· Runs commands
- T1064
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1129· Loads modules
- T1202
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1543.002· Service install
- T1562.001· Disables security
- T1564· Hides artifacts
- T1564.001· Hides artifacts
- T1564.003· Hides artifacts
Observed activity
Processes started
3Programs the file ran, with their command lines.
javaw.exe"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.jar"cmd.exeC:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\download.jar"" >> C:\cmdlinestart.log 2>&1java.exe"C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -javaagent:"C:\Users\user\AppData\Local\Temp\jartracer.jar" -jar "C:\Users\user\Desktop\download.jar"
Files
15Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6064 - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp - Written
C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user - Written
C:\Users\user\AppData\Local\Temp\hsperfdata_user\2788 - Written
C:\cmdlinestart.log
Show all 15 entries for files
- Written
\Device\ConDrv\\Connect - Written
/proc/3547/coredump_filter - Written
/tmp/hsperfdata_root/3547 - Written
/var/log/auth.log.1.gz - Written
/var/log/dpkg.log.1.gz - Written
/var/log/kern.log.1.gz - Written
/var/log/syslog.1.gz - Deleted
C:\Users\user\AppData\Local\Temp\hsperfdata_user\4784 - Deleted
/tmp/hsperfdata_root/3547
Sandbox background — not the file
12The analysis machine's own processes and connections, recorded in every run.
- VM process
icacls.exeC:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M - VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM process
gzip/bin/gzip - VM process
sh/bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log " - VM process
invoke-rc.d/usr/sbin/invoke-rc.d invoke-rc.d --quiet cups restart - VM process
runlevel/sbin/runlevel
Show all 12 entries for sandbox background — not the file
- VM process
systemctl/usr/bin/systemctl systemctl --quiet is-enabled cups.service - VM process
ls/usr/bin/ls ls /etc/rc[S2345].d/S[0-9][0-9]cups - VM process
systemctl/usr/bin/systemctl systemctl --quiet is-active cups.service - VM process
sh/bin/sh sh -c /usr/lib/rsyslog/rsyslog-rotate logrotate_script /var/log/syslog - VM process
rsyslog-rotate/usr/lib/rsyslog/rsyslog-rotate - VM process
systemctl/usr/bin/systemctl systemctl kill -s HUP rsyslog.service
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- b0176234c37dcf23e3c1…39799dNot checkedno saved verdict
- 7b3c273af2023b41081c…523f05Not checkedno saved verdict
- 253e796a303869157431…3ae8feNot checkedno saved verdict
Chapter 04
Technical details
None of the 64 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 31, 2026, 3:29 AM UTC
- SHA-256
0cd17699529624a1828957e5de36b0bdf240643b05f24a130ce1d0c2ab3c8320- SHA-1
d1a9895d7b2da9bbdee01175bfde738c5861bd35- MD5
ea13cbe413fb3b8871c2e4e071f65736
About this file
4ENEVERSEENBEFOREBYRAIN.jar is a JAR file of 487.9 kB.
- Type and size
- JAR · 487.9 kB
- Signer
- Not applicable
- First seen
- Jul 4, 2026On VirusTotal.
- Submitted by
- 28 distinct sources
First scanned
Antivirus consensus
0 of 64 engines flagged this file
11 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-234 engines0flagged
- Low-trust13 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneNo result
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is 4ENEVERSEENBEFOREBYRAIN.jar safe?
What is 4ENEVERSEENBEFOREBYRAIN.jar?
How many antivirus engines detected 4ENEVERSEENBEFOREBYRAIN.jar?
What is the SHA-256 hash of 4ENEVERSEENBEFOREBYRAIN.jar?
Is it safe to open or run 4ENEVERSEENBEFOREBYRAIN.jar?
How up to date is this analysis of 4ENEVERSEENBEFOREBYRAIN.jar?
Community
Member reviews and reports for this exact file hash.