File scan report
Verdict Suspicious
Is Numby- Hack- 2. 6. 24. jar. disabled safe? Treat it as suspicious.
All 64 antivirus engines that checked it produced no malicious or suspicious detection, including 17 major contributors, and the sandbox issued no malicious verdict.
Read the whole reasonShow less
Why Suspicious? Runtime recorded offensive techniques and T1562.001.
Limited evidence · One sign points to a problem; nothing else confirms it.
Keep protection enabled and obtain the JAR from a verified source before use. If its origin cannot be established, delete it or examine it only in a network-restricted virtual machine.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
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 6mo ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The strongest evidence is the absence of detections across 75 antivirus engines, including all 17 major contributors. One completed sandbox run did not issue a malicious verdict, and none of the five inspected child hashes was identified as malicious. However, the run recorded and T1562.001, which can indicate service execution and interference with defenses. A low-severity rule also noted direct contact with 162.159.36.2, and no complete host-reputation result is available. The unsupported community claim of a named RAT or stealer family is insufficient to outweigh the independent evidence, but the runtime signals prevent an unqualified benign assessment.
What We Detected
No malicious or suspicious detection was returned by any of the 75 antivirus engines. This includes 17 major contributors, and no engine supplied a malware-family label. Researcher-curated sources also returned no CIRCL, MalwareBazaar, or YARAify match.
Threat Behavior
One sandbox run recorded T1543.002 and T1562.001, two techniques associated with service execution and impairment of defenses, although the sandbox did not issue a malicious verdict. The sample contacted 162.159.36.2 directly, triggering a low-severity heuristic. Because the contacted-host reputation check was not completed or saved, that connection cannot be characterized as benign or malicious. Five written child hashes were inspected; none was identified as malicious, but all five remain without definitive verdicts.
What To Do Now
Keep security software enabled and avoid running the JAR on a production or personal system until its origin is verified. If testing is necessary, use an isolated virtual machine, restrict network access, and inspect the JAR contents and Java entry point before execution.
Where this verdict could be wrong3 caveats
- The runtime recorded and T1562.001, techniques associated with service execution and impairment of defenses.
- The low-severity one of our behaviour rules recorded contact with 162.159.36.2, but host reputation was not checked or saved.
- communityComments[0] alleges WEEDHACK and RAT/stealer activity, but it has 0 votes and lacks corroboration from engines, sandbox verdicts, or external intelligence.
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/64 engines reported a malicious or suspicious detection.
- All 17 major contributors reported no detection.
- No sandbox returned a malicious verdict.
- No dropped file is known to be malicious.
- YARAify, CIRCL, and MalwareBazaar returned no hit.
- Runtime recorded offensive techniques and T1562.001.
- The filename includes “Hack,” but no hacking-tool label is corroborated and filename alone is not determinative.
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- 10sandbox rule tags
- 4spawned processes
- 0network contacts
- 13filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Hid files or windows on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
Numby-Hack-2.6.24.jar.disabled
1b612c3e3a8aea0cafaea5a5b231132267fa0815d8df4ee2b159ec4b753271bb
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
java.exe
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\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\runtime.jar"" >> C:\cmdlinestart.log 2>&1
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
2380
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2380
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 10 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 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
- Sep 8, 2026, 3:49 PM UTC
- SHA-256
1b612c3e3a8aea0cafaea5a5b231132267fa0815d8df4ee2b159ec4b753271bb- SHA-1
537522ab47983d6ab5c8dcb7808648dda73eea25- MD5
85aad9b8fb81753ce974e35ccdeb8707
About this file
Numby-Hack-2.6.24.jar.disabled is a JAR file of 261.8 kB.
- Type and size
- JAR · 261.8 kB
- Signer
- Not applicable
- First seen
- Apr 29, 2026On VirusTotal.
- Submitted by
- 114 distinct sources
First scanned
Includes every engine result (75) 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 Numby-Hack-2.6.24.jar.disabled safe, or is it malware?
What is Numby-Hack-2.6.24.jar.disabled?
How many antivirus engines detected Numby-Hack-2.6.24.jar.disabled?
What should I do if I already opened or ran Numby-Hack-2.6.24.jar.disabled?
What is the SHA-256 hash of Numby-Hack-2.6.24.jar.disabled?
How up to date is this analysis of Numby-Hack-2.6.24.jar.disabled?
Community
Member reviews and reports for this exact file hash.