LoFP LoFP / jvm defects, incompatible or vulnerable jni libraries, java agents, profilers, faulty native modules, hardware problems, and resource exhaustion can legitimately cause hotspot to terminate and write a fatal error log.

Techniques

Sample rules

Java HotSpot Fatal Error Log Created

Description

Identifies the creation of a Java HotSpot fatal error log by a Java process. The JVM writes “hs_err_pid*.log” after a fatal error, such as an access violation, segmentation fault, or unrecoverable native-code failure. This may indicate an unsuccessful attempt to exploit a Java memory-corruption vulnerability. In particular, failed Java4Shell (CVE-2026-114938) heap-grooming or corruption attempts may crash the JVM before remote code execution succeeds. This event indicates a JVM crash and possible exploit attempt; it does not by itself establish successful exploitation or remote code execution.

Detection logic

file where host.os.type in ("windows", "linux", "macos") and
  event.type == "creation" and
  process.name : "java*" and
  file.name : "hs_err_pid*.log"