Zeek HTTP Malformed Base64 Padding: networkNetworkNoneversion:1
The analytic hunts for an HTTP header, POST body, or URI containing at least one 64-character Base64 block followed by a short padded fragment. This malformed shape can reach a vulnerable Java Base64 decoder, but its presence in traffic alone does not prove that the server decoded it.
HTTP Base64 Activity With JVM Errors: endpointEndpointNoneversion:1
The analytic associates each Zeek request containing a malformed Base64 value or a scripted decoder trigger with a nearby Base64-related HotSpot argument exception on the same server and Java PID.
Sysmon child process, file creation, or process termination events from that PID add context and can raise confidence.
Java Base64 Exception With Process or File Activity: endpointEndpointNoneversion:1
The analytic finds Base64-related Java argument exceptions near a process spawned by Java or a file created by Java on the same host and JVM PID.
Java Base64 Decoder Argument Exceptions: endpointEndpointNoneversion:1
The analytic finds Java Base64 decoder references and argument exceptions on the same JVM process within one minute. JIT messages add context when present. These logs indicate decoder activity and errors, but do not prove that a native overwrite or code execution occurred.