Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Offensive and testing tools

What Is JavaChains? The Java Deserialization Exploit Server Explained

A web platform that packages Java deserialization and JNDI attacks into point-and-click payloads and callback servers: how it works, where Odin found it, and how to shut it out.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Java exploit server (dual-use)

In short

JavaChains is an open-source web platform that generates Java deserialization payloads and runs the callback servers that deliver them, such as JNDI, LDAP, RMI and fake MySQL listeners. Researchers use it to test Java applications. Attackers use the same servers to make vulnerable apps load remote code. Its web interface listens on port 8011.

Key takeaways

What it is
An open-source Java payload generation and exploitation platform published by the vulhub project on GitHub, for security research.
How it works
A web console on port 8011 builds gadget-chain payloads. Built-in JNDI, LDAP, RMI, JRMP and fake MySQL listeners hand malicious Java classes to apps that deserialize untrusted data.
Why it matters
One unsafe parser, such as an old SnakeYAML constructor (CVE-2022-1471), can let an attacker load and run remote Java code.
What Odin Research saw
42 JavaChains endpoints on 41 hosts in Monograph 23. 38 (90.5%) listened on port 8011, and 16 were confirmed and published for blocking.
What to do first
Block outbound LDAP, RMI and JNDI callbacks from Java servers, turn on serialization filters, upgrade SnakeYAML to 2.0 or later, and block the confirmed servers.

What is JavaChains?

JavaChains is an open-source web platform that generates Java deserialization payloads and runs the callback servers that deliver them. Its JNDI, LDAP, RMI, JRMP and fake MySQL listeners hand malicious Java classes to applications that trust incoming data. Researchers use it for testing. Attackers use it to load remote code into vulnerable Java apps.

The project is published on GitHub as vulhub/java-chains. Its README describes a Java payload generation platform for security researchers. The web interface supports common payload generation plus JNDI, fake MySQL and JRMP testing. It credits earlier open-source projects such as ysoserial and marshalsec. The README states that the tool is for personal research and learning only.

The repository had about 2,200 stars and 174 forks on 21 November 2026. Its examples reference version 2.0.2.

JavaChains is a dual-use tool. In a lab it shows whether a Java service is exploitable. On a public cloud server it can be the delivery stage of public-facing application exploitation.

How JavaChains works

Many Java applications turn incoming bytes or text back into objects. This is deserialization. If the application accepts any class, an attacker can send a chain of ordinary library classes, a "gadget chain", that ends in code execution. The ysoserial README stresses that the flaw lies in the unsafe deserialization, not in the libraries themselves. Other bugs make an application look up a remote object through JNDI and load a class from the attacker's server. Our page on JNDI injection covers that pattern, and Log4Shell is its best-known example.

JavaChains packages both halves:

  1. Payload builder. The web console generates payloads. Monograph 23 lists gadget generation for CommonsCollections, CommonsBeanutils, Fastjson, Jackson, Hessian and SnakeYAML.
  2. Callback servers. The README lists port 8011 for the web interface, and separate default ports for JNDI over HTTP, LDAP and RMI, a fake MySQL server, a JRMP listener, and generic HTTP and TCP services.

A vulnerable target receives a payload, then calls back to one of these listeners and pulls a second-stage Java class. Monograph 23 explains why this matters: a simple proof of concept carries one hard-coded command, while an integrated weaponizer runs all listeners at once.

The README recommends Docker, with the image javachains/javachains, or a standalone JAR on JDK 8. Authentication is on by default. If no password is set, a random one is generated at startup and printed in the log.

JavaChains, SnakeYAML and CVE-2022-1471

One flaw shows how these payloads land. CVE-2022-1471 affects SnakeYAML, a common Java YAML library. NVD says its Constructor() class does not restrict which types it creates, so attacker-supplied YAML can lead to remote code execution. NVD scores it 9.8 (Critical) under CVSS 3.1, and the CNA scores it 8.3 (High). The fix is SafeConstructor for untrusted input and an upgrade to SnakeYAML 2.0 or later.

Monograph 23 found a workbench that applied this flaw to RuoYi, a popular open-source Java admin framework. Its scheduled-task feature can pass attacker text to SnakeYAML. The staged project was designed to load a remote code archive and register an in-memory filter on routes such as /login. No JSP file is written to disk, so file-based web shell scans miss it.

What Odin Research observed

Monograph 23 mapped JavaChains alongside Responder NTLM traps and ICMP tunnels in a two-week window ending 18 November 2026.

  • A port-8011 fleet. Odin Research found 42 JavaChains endpoints on 41 hosts. 38 (90.5%) listened on port 8011, 2 on 8012, and one each on 443 and 80.
  • Concentrated in Chinese clouds. 36 of the 42 endpoints sat in China. The 16 confirmed servers ran on dedicated hosting: 8 on Shenzhen Tencent, 5 on Hangzhou Alibaba, and one each on Volcano Engine, UCloud in Hong Kong and Hetzner in Germany.
  • Blocked, with care. The 16 confirmed servers were published for blocking. Three more sat on Chinese home-broadband networks, where addresses change hands, so they went on a short watchlist.
  • Two workbenches. One held the RuoYi SnakeYAML builder next to an ARL reconnaissance worker. The other held 123 files for replaying raw HTTP exploits, including a 317.8 MB log of out-of-band callbacks.
  • Intent, not outcome. These are staged tools and attacker logs. Odin Research did not confirm an exploit against any specific target.

Monograph 02 also saw a JavaChains candidate on port 8011 next to ARTEX on one host, a reminder that offensive tools often share servers.

How to detect JavaChains

  • Outbound callbacks. A Java server that opens LDAP, RMI or HTTP connections to an unknown internet host right after receiving a request is the core signal of JNDI or deserialization abuse.
  • Class files on the wire. An HTTP response whose body starts with the Java class magic bytes CA FE BA BE and references java/lang/Runtime is a class with command execution.
  • Serialized data in requests. OWASP notes that Java serialized data starts with hex AC ED 00 05, or rO0 in Base64. Flag these in requests to apps that should not accept them.
  • Control-plane traffic. An internal host that sends POST /api/chain/ requests with a "gadget" field to port 8011, 8012 or 443 is driving a JavaChains console.
  • Processes. On Linux, java, mvn or shells whose command lines name javachains or a RuoYi YAML payload project.

Monograph 23 publishes Suricata signatures, a Sentinel KQL hunt, a Sigma rule and a YARA rule for JavaChains configs and the RuoYi builder. Find them in the Defense Kit.

How to defend against JavaChains attacks

  1. Block Java egress. Java application servers rarely need outbound LDAP or RMI. Deny it, and allow outbound HTTP only to known hosts.
  2. Filter deserialization. OWASP recommends Java serialization filters with an application-specific allowlist, look-ahead checks on expected classes, and plain data formats such as JSON for untrusted input. It also warns that filtering does not make arbitrary untrusted deserialization safe.
  3. Patch libraries. Upgrade SnakeYAML to 2.0 or later and use its safe loader. Track library flaws with an SBOM.
  4. Block the confirmed servers. Monograph 23 lists 16 confirmed JavaChains addresses. Review blocks after 30 days, as cloud addresses get reassigned.
  5. Hunt for memory shells. If a Java app was exposed, look for unexpected filters or listeners registered at runtime. See How to respond to actively exploited vulnerabilities.

JavaChains compared with other Java exploit tools

ToolWhat it doesCallback serversInterface
JavaChainsBuilds gadget-chain payloads and serves second-stage classesYes: JNDI over HTTP, LDAP and RMI, JRMP, fake MySQLWeb console on port 8011
ysoserialGenerates serialized Java payloads from known gadget chainsNo; writes the payload to standard outputCommand-line JAR
marshalsecResearch project on Java unmarshalling, with payload generatorsYes: LDAP and RMI JNDI reference serversCommand-line JAR
Single PoC exploitsOne hard-coded command for one bugUsually noneScript

The difference that matters to defenders is the callback layer. An integrated platform keeps several listeners running, so egress control blocks the whole class of attack at once.

Frequently asked questions about JavaChains

What is JavaChains?

JavaChains is an open-source web platform for generating Java deserialization payloads and running JNDI, LDAP, RMI, JRMP and fake MySQL callback servers. It is published by the vulhub project for security research.

Is JavaChains malware?

No. It is a research and testing tool. It is dual-use: the same servers can deliver malicious Java classes to real vulnerable applications, which is why Odin Research published confirmed hostile servers for blocking.

Is JavaChains legal to use?

Using it in your own lab or on systems you are authorized to test is legal. Its README says it is for personal research and learning only. Attacking systems without permission is a crime.

What port does JavaChains use?

The web interface listens on port 8011 by default. Odin Research found 38 of 42 JavaChains endpoints on 8011. The callback listeners use their own ports.

Who made JavaChains?

It is published on GitHub under the vulhub organization as java-chains. The README credits earlier projects such as ysoserial and marshalsec.

What is a gadget chain?

A gadget chain is a sequence of ordinary library classes that, when deserialized in order, ends in an action such as running a command. JavaChains generates chains for common Java libraries.

How do I detect JavaChains attacks?

Watch for Java servers making outbound LDAP, RMI or HTTP callbacks, responses carrying Java class files, and serialized Java data in requests. Odin Research publishes Suricata, Sigma, YARA and KQL rules in its Defense Kit.

JavaChains vs ysoserial: what is the difference?

ysoserial generates deserialization payloads from the command line. JavaChains adds a web console and the callback servers that deliver second-stage classes, and it credits ysoserial as a source.

How do I protect Java applications from JavaChains?

Block outbound LDAP and RMI from Java servers, use serialization filters and safe parsers, upgrade SnakeYAML to 2.0 or later, and avoid native Java deserialization of untrusted input.

Sources

  1. vulhub, Java Chains repository and README, GitHub. github.com/vulhub/java-chains (checked 21 November 2026)
  2. frohoff, ysoserial repository, GitHub. github.com/frohoff/ysoserial (checked 21 November 2026)
  3. mbechler, marshalsec repository, GitHub. github.com/mbechler/marshalsec (checked 21 November 2026)
  4. NVD, CVE-2022-1471. nvd.nist.gov/vuln/detail/CVE-2022-1471 (checked 21 November 2026)
  5. OWASP, Deserialization Cheat Sheet. cheatsheetseries.owasp.org/cheatsheets/Deserialization_Cheat_Sheet.html (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit