Is 198-Macros-Cracked-v1.4.0.jar safe?
Single tier-1 engine flags this JAR as GameTool while sandbox shows process-injection techniques but no malicious verdict.
One high-trust engine labels the file Java/GameTool.AG; sandbox captured T1055 process injection and persistence attempts yet returned no malicious verdict. Medium prevalence and research-tool filename pattern keep the risk borderline.
1c41d33235e945a0fd…3c725558eeaadbRecommended next actions
Before opening or running
Do not open or run it until the source and publisher can be verified independently.
If you already opened or ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the publisher's official site 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.
One high-trust engine labels the file Java/GameTool.AG; sandbox captured T1055 process injection and persistence attempts yet returned no malicious verdict. Medium prevalence and research-tool filename pattern keep the risk borderline.
The single tier-1 detection is offset by 16 clean tier-1 engines and the absence of sandbox or child-file malice. Offensive MITRE techniques raise concern, but without host-reputation data or external-intel corroboration the evidence remains mixed. Filename and heuristic signals point to a research or cracking tool rather than commodity malware.
What We Detected
One tier-1 engine (ESET-NOD32) flagged the JAR as Java/GameTool.AG. Sandbox execution recorded MITRE techniques T1055 (process injection), T1543.002 (new service), and T1562.001 (impair defenses). Eight dropped files were inspected; none carried malicious verdicts.
Threat Behavior
The sample writes temporary Java hsperfdata files, adjusts ACLs on Oracle JRE usage folders, and spawns additional Java processes via javaagent. No C2 domains were observed; a single direct IP contact lacks reputation context because contactedHosts is null.
What To Do Now
Keep endpoint protection enabled. If the file is not required, delete it and clear the Java temp directories. Avoid executing JARs from untrusted sources; scan any similar files before use.
Where this verdict could be wrong2 caveats
- Single tier-1 detection with no family consensus; 16 other tier-1 engines reported clean.
- Sandbox showed no malicious verdict and droppedChildren.hasMaliciousChild=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16 tier-1 engines reported clean
- No malicious dropped children
- No external-intel hits
- Process-injection capability (T1055)
- Persistence-related service creation (T1543.002)
- Defense-evasion actions (T1562.001)
- Direct-IP contact without domain reputation
Treat as potentially unwanted; do not run without a clear, trusted source and keep all security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
Complete2 signature or behavior rules 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
- 16MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 14filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Transferred a file over the network; malware can use this to fetch additional payloads.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
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
198-Macros-Cracked-v1.4.0.jar
1c41d33235e945a0fd920385d81466aef8da154eaeb6433cb63c725558eeaadb
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.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
5736
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5736
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>\5736
- 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\6932
- /tmp/hsperfdata_root/3534
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- b1daca2d7aff12059626…900450Never scannednever seen before
- 4f6111dfffaf5b5905cd…4e75f0Never scannednever seen before
- 88c51b11848142e935cf…e27b2eNever scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 61625fd8b084f70f242d…55abd2Never scannednever seen before
- 50c82f36208ed8040447…2d7843Never scannednever seen before
- 8e8711854186c68e2368…4a3c7cNever scannednever seen before
- 759aafcfa2395ce1b800…2af0f7Never 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.
- 2rule hits recorded
- 1 / 75engines flagged
- 69sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including ESET-NOD32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 75 times from 69 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: 198-Macros-Cracked-v1.4.0.jar — 1c41d33235e945a0fd920385d81466aef8da154eaeb6433cb63c725558eeaadb
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 5736 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5736
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"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
1 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
- 198-Macros-Cracked-v1.4.0.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 17.9 KB
- Last analyzed
- Sep 4, 2026, 3:22 PM UTC
1c41d33235e945a0fd920385d81466aef8da154eaeb6433cb63c725558eeaadbSafety & 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 or run 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 Java file and use a fresh copy from a trusted source. Get a fresh copy from the publisher's official site 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 198-Macros-Cracked-v1.4.0.jar safe, or is it malware?
What is 198-Macros-Cracked-v1.4.0.jar?
How many antivirus engines detected 198-Macros-Cracked-v1.4.0.jar?
What should I do if I already opened or ran 198-Macros-Cracked-v1.4.0.jar?
How do I remove 198-Macros-Cracked-v1.4.0.jar?
What kind of malware is 198-Macros-Cracked-v1.4.0.jar?
What is the SHA-256 hash of 198-Macros-Cracked-v1.4.0.jar?
How up to date is this analysis of 198-Macros-Cracked-v1.4.0.jar?
Community
Member reviews and reports for this exact file hash.