Is Numby-Hack-2.6.24.jar.disabled safe?
No antivirus engine detected the JAR, but two offensive runtime techniques and unverified direct-IP traffic warrant caution pending deeper inspection.
All 75 antivirus engines produced no malicious or suspicious detection, including 17 tier-1 contributors, and the sandbox issued no malicious verdict. However, runtime evidence includes two offensive techniques and contact with an IP whose reputation was not checked, so execution should remain isolated until the source and behavior are verified.
1b612c3e3a8aea0caf…59ec4b753271bbRecommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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 produced no malicious or suspicious detection, including 17 tier-1 contributors, and the sandbox issued no malicious verdict. However, runtime evidence includes two offensive techniques and contact with an IP whose reputation was not checked, so execution should remain isolated until the source and behavior are verified.
The strongest evidence is the absence of detections across 75 antivirus engines, including all 17 tier-1 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 T1543.002 and T1562.001, which can indicate service execution and interference with defenses. A low-severity heuristic 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 tier-1 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 endpoint protection 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 T1543.002 and T1562.001, techniques associated with service execution and impairment of defenses.
- The low-severity MalwareTips.Synth.DirectIpC2 heuristic 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/75 engines reported a malicious or suspicious detection.
- All 17 tier-1 contributors reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, CIRCL, and MalwareBazaar returned no hit.
- Runtime recorded offensive techniques T1543.002 and T1562.001.
- Direct-IP contact to 162.159.36.2 lacks a completed reputation check.
- All five inspected child hashes have unknown verdicts.
- The filename includes “Hack,” but engines.hacktoolConfirmed=false and filename alone is not determinative.
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.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 10MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 13filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
Note: Connected to 1 server during sandbox analysis.
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
Numby-Hack-2.6.24.jar.disabled
1b612c3e3a8aea0cafaea5a5b231132267fa0815d8df4ee2b159ec4b753271bb
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
2380
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2380
04Isolated runtime analysis - Written fileObserved
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2380
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\7104
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\5908
- /tmp/hsperfdata_root/5000
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- bcb66501e0a1bf3acb34…fae6ebNever scannednever seen before
- a6d4531ba0cb26d12cdf…2043adNever scannednever seen before
- 3f8096f14540c8e18e4e…ad10b8Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 114sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 125 times from 114 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Numby-Hack-2.6.24.jar.disabled — 1b612c3e3a8aea0cafaea5a5b231132267fa0815d8df4ee2b159ec4b753271bb
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: 2380 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2380
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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 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
- Numby-Hack-2.6.24.jar.disabled
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 255.6 KB
- Last analyzed
- Sep 8, 2026, 3:49 PM UTC
1b612c3e3a8aea0cafaea5a5b231132267fa0815d8df4ee2b159ec4b753271bbSafety & 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 open 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 original trusted source and verify its exact hash when possible.
- 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 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 Numby-Hack-2.6.24.jar.disabled?
How do I remove 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.