Suspicious
Unsigned JAR shows direct-IP contact and two offensive MITRE techniques but zero antivirus detections and a clean community verdict.
0ba5c89b4873e2a24a…d0bb3390fdThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
The complete absence of malicious detections across tier-1 and tier-2 engines strongly favors a benign or low-risk classification. However the sandbox observed direct IP contact without DNS resolution and recorded two techniques commonly abused by malware for persistence and defense evasion. Medium prevalence and an explicit researcher comment labeling the sample clean offset the heuristic concern, resulting in a borderline suspicious verdict rather than outright malicious or safe.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines: 0/59 malicious (tier1Malicious=0, onlyLowTrustFlagging=false)
triggeredHeuristics: MalwareTips.Synth.DirectIpC2 fired on IP 162.159.36.2
behaviour.offensiveTechniques: T1543.002 and T1562.001 present
communityComments[0].text: 'Verdict: **Clean** Score: **0/100**'
prevalence.classification: medium (306 submitters)
- Zero malicious detections across 59 engines
- Medium prevalence with 306 submitters
- Explicit community clean verdict
- Direct IP contact without DNS (DirectIpC2 heuristic)
- Offensive MITRE techniques T1543.002 and T1562.001
- Unsigned JAR
Treat as suspicious until additional runtime telemetry or updated AV coverage clarifies intent; do not execute on production systems without isolation.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Installs itself as a Windows service to stay running.
High concern: Tries to disable or bypass your security software.
Moderate concern: Checks which security software you have installed.
Moderate concern: Connects out to 1 server on the internet.
Note: Collects details about your system.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
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>\6956
- 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\1220
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6808
- /tmp/hsperfdata_root/5006
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 698f7e50cd92e670b729…3a5023Never scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never scannednever seen before
- ac941ead01d5451a7a9f…253227Never scannednever seen before
YARA & heuristic rule matches
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 1 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence162.159.36.2
0 detections across 75 engines
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Forensic fingerprint
- File name
- Argon.jar
- Size
- 334.7 KB
- MIME type
- (unknown)
- Detected type
- JAR
- SHA-256
- 0ba5c89b4873e2a24a31d316a090cc98353ee1d04881695cafee18d0bb3390fd
- MD5
- 8f57ba7e132968ec75473e6f0e7b71b3
- SHA-1
- 39b697a348d8f711eb9aeb9b7d914faf8642a6ed
- First seen (VT)
- 12/2/2025, 11:42:46 AM
- Last analysis (VT)
- 5/8/2026, 7:19:52 AM
- First scan (MalwareTips)
- 5/17/2026, 7:24:27 PM
- Last scan (MalwareTips)
- 5/17/2026, 7:24:27 PM
Safety FAQ
Common questions about Argon.jar, answered from the scan data above.
- Argon.jar is suspicious — treat it as unsafe until you're sure. 0 of 75 antivirus engines flag it, which isn't a strong consensus but is enough to be cautious. Don't opened it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- Argon.jar is a file, about 335 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- None — all 75 antivirus engines we queried report Argon.jar as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove Argon.jar: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original Argon.jar file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- The SHA-256 hash of Argon.jar is 0ba5c89b4873e2a24a31d316a090cc98353ee1d04881695cafee18d0bb3390fd, and its MD5 is 8f57ba7e132968ec75473e6f0e7b71b3. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on May 17, 2026. Because a file's hash never changes, the identity of Argon.jar is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
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.