MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 1 month ago

Is 198-Macros-Cracked-v1.4.0.jar safe? Treat it as suspicious.

A major engine identifies this uninspected Java archive as a potentially unsafe game tool, but the remaining evidence neither confirms malware nor establishes a trusted origin.

Read the whole reasonShow less

Why Suspicious? One antivirus engine (ESET) flags it; nothing else confirms it.

Limited evidence

Don't open or run it until you know where it came from

If it came from a link, an attachment or a stranger, delete it.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't open or run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

198-Macros-Cracked-v1.4.0.jar: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

1 of 65 flagged

  • Flagged 1
  • No detection 64
  • No result 10
File198-Macros-Cracked-v1.4.0.jar18.3 kBSHA-256 1c41d33235e9…eeaadb
  • Code signing Not applicable
  • Test run Completed
  • First seen 2mo ago
1 of the 65 antivirus engines that checked it flags it (ESET).

Chapter 02

Why we think so

4 points against it and 4 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

One of the 65 antivirus engines that checked it, ESET-NOD32, identifies this Java archive as a potentially unsafe game tool; the other reported results do not corroborate that label. Because its crack-style name raises concern and its compressed classes were not examined by our static analysis, there is not enough evidence to establish either harmful code or a trustworthy release.

Where this verdict could be wrong3 caveats
  • Only one of the 65 antivirus engines that checked it flagged the file, while 17 other major engines reported no detection.
  • The sandbox runs recorded no named injection target, no malicious verdict, and no high-risk technique with supporting evidence.
  • The file has been submitted by 69 distinct sources, although that distribution alone does not verify its origin or contents.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

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
  • 14filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Hid files or windows on the test computer.

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Loaded extra code modules while running.

  • 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 code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as downloading a file, but no download was recorded.

  • 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.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 5: FileSeen in the test run

      198-Macros-Cracked-v1.4.0.jar

      1c41d33235e945a0fd920385d81466aef8da154eaeb6433cb63c725558eeaadb

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 5: ProcessSeen in the test run

      javaw.exe

      "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"

      Test run
    2. 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\sample.jar"" >> C:\cmdlinestart.log 2>&1

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 5: Written fileSeen in the test run

      5736

      C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5736

      Test run
    2. Evidence 5 of 5: Written fileSeen in the test run

      3903daac9bc4a3b7.timestamp

      C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp

      Test run
    3. +1 more recorded observation

5 facts from the test run. See the full activity list.

Chapter 04

Technical details

1 of the 65 antivirus engines that checked it flags 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 1 of 65 engines flagged it · 10 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 1

  • ESET-NOD32 (major engine)Java/GameTool.AG potentially unsafe application

File fingerprint

Last analyzed
Sep 4, 2026, 3:22 PM UTC
SHA-256
1c41d33235e945a0fd920385d81466aef8da154eaeb6433cb63c725558eeaadb
SHA-1
6b2ff603257352262838bec8dfc94fa6a49e4963
MD5
38fed1657ec7f675651d6013e534b561

About this file

198-Macros-Cracked-v1.4.0.jar is a JAR file of 18.3 kB.

Type and size
JAR · 18.3 kB
Signer
Not applicable
First seen
Aug 11, 2026On VirusTotal.
Submitted by
69 distinct sources

First scanned Updated

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is 198-Macros-Cracked-v1.4.0.jar safe, or is it malware?
198-Macros-Cracked-v1.4.0.jar is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 1 of the 65 antivirus engines that checked it flags it. Don't open or run it unless you're sure where it came from. If you need it, download it again from the project's own website.
What is 198-Macros-Cracked-v1.4.0.jar?
198-Macros-Cracked-v1.4.0.jar is a Java program (JAR), about 18.3 kB. VirusTotal first saw it on Aug 11, 2026.
How many antivirus engines detected 198-Macros-Cracked-v1.4.0.jar?
1 of the 65 antivirus engines that checked it flags 198-Macros-Cracked-v1.4.0.jar (ESET). We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already opened or ran 198-Macros-Cracked-v1.4.0.jar?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of 198-Macros-Cracked-v1.4.0.jar?
The SHA-256 fingerprint of 198-Macros-Cracked-v1.4.0.jar is 1c41d33235e945a0fd920385d81466aef8da154eaeb6433cb63c725558eeaadb, and its MD5 is 38fed1657ec7f675651d6013e534b561. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of 198-Macros-Cracked-v1.4.0.jar?
This report reflects the scan on Sep 4, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.