Suspicious Java Class File Created in PaperCut Server Library
Description
Detects creation of Java .class files within the PaperCut NG/MF Application Server library directory. During active exploitation of CVE-2026-82078 (chained with CVE-2026-81578), attackers deliver hex-encoded malicious .class payloads into the PaperCut server/lib path (observed examples include Udydn.class and Moo97.class) so arbitrary bytecode executes inside the PaperCut JVM / Application Server process.
Query · eql
file where host.os.type in ("windows", "linux", "macos") and
event.action in ("creation", "overwrite") and
file.extension : "class" and
file.path : (
"?:\\Program Files\\PaperCut*\\server\\lib\\*",
"?:\\Program Files (x86)\\PaperCut*\\server\\lib\\*",
"/opt/papercut/server/lib/*",
"/usr/local/papercut/server/lib/*",
"/Applications/PaperCut*/server/lib/*"
)
Investigation fields
Pivot points the source recommends for triage.
@timestamphost.idhost.namehost.os.typeuser.iduser.nameprocess.nameprocess.executablefile.pathfile.namefile.size
Implementation guide
This rule is designed for data generated by Elastic Defend, which provides native endpoint detection and response, along with event enrichments designed to work with our detection rules.
Setup instructions: https://ela.st/install-elastic-defend
Analyst notes
Investigating Suspicious Java Class File Created in PaperCut Server Library
PaperCut NG/MF loads database/driver-related classes from the Application Server classpath. CVE-2026-82078 allows unsafe
dynamic class loading when configuration can be manipulated (enabled by CVE-2026-81578 authentication bypass). Huntress
recovered attacker .class files written under server\lib (for example Udydn.class, Moo97.class) that decoded
commands, wrote output under server\data\content, then deleted staging files and often server.log.
Possible investigation steps
- Inspect
file.path,file.name,file.size, and writingprocess.executable/process.name. Unexpected short or random.classnames underserver/libare high confidence. - On the same host, look for companion artifacts under
server/data/content(.cmd,.out) and for suspiciouspc-app.exe/ Java child processes (shells,whoami,tasklist,charmap.exe). - Review PaperCut
server/logsfor hex-encoded blobs, base64 command strings,jdbc:derby:memory:pwn, Derby boot paths containing\pwn, orERROR No suitable driver found for jdbc:no:x. Note missing/truncatedserver.logfiles. - Confirm whether a PaperCut upgrade or emergency patch was running at
@timestamp; legitimate upgrades also write many.classfiles underserver/lib. - Scope other PaperCut servers for the same file names/paths and review internet exposure of the management interface.
False positive analysis
- PaperCut installation, upgrade, and emergency patch operations legitimately create
.classfiles underserver/lib. Correlate with change tickets, installer process names, and volume of writes before treating as malicious. - Exclude only tightly scoped upgrade processes/paths after validation; do not blanket-exclude the
server/libdirectory.
Response and remediation
- Restrict public access to the PaperCut Application Server immediately.
- Preserve
server/lib.classfiles,server/logs,server/data/content, and process telemetry before cleanup or patch. - Remove unauthorized
.classpayloads after evidence collection; apply PaperCut Emergency Patch Release 2 (or newer). - Hunt for related child-process activity from
pc-app.exeand rotate credentials if exploitation is confirmed.