MalwareTips
Threat LensFile scan report

Is Autobuilder-1.21.jar safe?

Verdict
Suspicious

Three tier-1 engines detected a Java trojan, while runtime telemetry mapped to process injection, service creation, and possible impairment of defenses.

Three of 75 engines flagged this JAR, with ESET-NOD32 and Fortinet independently naming Java/Agent.ADG. Its recent, scarce distribution and three offensive runtime techniques warrant isolation, although the sandbox did not issue a malware finding and no family reached strong tier-1 consensus.

Do not open or run it until verified

Quarantine the file and do not execute it unless its origin and integrity can be verified through the publisher's official channel. Keep endpoint protection enabled and scan the system if the JAR has already run.

Read the full analysis
Saved file evidenceAntivirus consensus
3of 75 flagged
Flagged 3No detection 72
Digital specimenAutobuilder-1.21.jar562cb76ba77b374bad…0cbe1e5c574d00
Size905.3 KB
Code signingNot applicable
SandboxRuntime complete
First seen1d ago
Evidence3 priority signals
1 high-confidence signature or behavior rule matched this file.

Recommended next actions

01

Before opening or running

Do not open or run it until the source and publisher can be verified independently.

02

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.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

82%Confidence
High
Analyst conclusion

Three of 75 engines flagged this JAR, with ESET-NOD32 and Fortinet independently naming Java/Agent.ADG. Its recent, scarce distribution and three offensive runtime techniques warrant isolation, although the sandbox did not issue a malware finding and no family reached strong tier-1 consensus.

Where this verdict could be wrong4 caveats
  • 14 of 17 reporting tier-1 engines did not detect the file, and engines.tier1FamilyConsensus.strong=false.
  • The single completed sandbox assigned a clean result, so behaviour.hasMaliciousSandboxVerdict=false.
  • droppedChildren inspected 8 hashes and found no confirmed malicious child, although all eight child verdicts remain unknown.
  • externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage gaps.

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

Recommended action

Quarantine the file and do not execute it unless its origin and integrity can be verified through the publisher's official channel. Keep endpoint protection enabled and scan the system if the JAR has already run.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    3 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded

  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 16MITRE ATT&CK techniques
  • 15spawned processes
  • 0network contacts
  • 15filesystem & 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: Contained obfuscated or packed code that makes inspection harder.

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

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.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Don't open or run it unless you're certain it came from a source you trust.

  2. Recovery step 02

    Check where you got it — an unexpected attachment or a random download link is a red flag.

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

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

8 evidence-based answers
Is Autobuilder-1.21.jar safe, or is it malware?
Evidence-based answer
Autobuilder-1.21.jar is suspicious — treat it as unsafe until you're sure. 3 of 75 antivirus engines flag it (family: Java Agent ADG); that detection signal contributes to the cautious verdict. Don't open or run it unless you fully trust where it came from. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
What is Autobuilder-1.21.jar?
Evidence-based answer
Autobuilder-1.21.jar is a Java application or archive, about 905 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.
How many antivirus engines detected Autobuilder-1.21.jar?
Evidence-based answer
3 of 75 antivirus engines flagged Autobuilder-1.21.jar, 3 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence.
What should I do if I already opened or ran Autobuilder-1.21.jar?
Evidence-based answer
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.
How do I remove Autobuilder-1.21.jar?
Evidence-based answer
To remove Autobuilder-1.21.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 this Java file from the device, then empty the Recycle Bin or 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.
What kind of malware is Autobuilder-1.21.jar?
Evidence-based answer
Autobuilder-1.21.jar is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the Java Agent ADG family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
What is the SHA-256 hash of Autobuilder-1.21.jar?
Evidence-based answer
The SHA-256 hash of Autobuilder-1.21.jar is 562cb76ba77b374bad99c1222b1ca235ae9fc4d7fc377014750cbe1e5c574d00, and its MD5 is cb52c5db3f58b734f3c99d08cbed72dc. 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.
How up to date is this analysis of Autobuilder-1.21.jar?
Evidence-based answer
This report reflects the scan run on September 26, 2026. Because a file's hash never changes, the identity of Autobuilder-1.21.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.
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
The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.