1-minute read
What a defender needs to know
Hunt.io recovered five Hermes task logs from an exposed server used in activity associated with systems at Thailand’s Ministry of Finance. The ministry has not publicly confirmed the reported compromise, and the researchers could not determine how the operator gained initial access.
The logs record privilege checks, service discovery, SUID and SGID searches, container and filesystem inspection, and recursive file enumeration while Hermes ran in unattended mode. Hunt.io found no evidence that inventoried office files were exfiltrated. Other material on the server, including exploit code, GlassFish deployment scripts, Hades implant builds and VShell payloads, was staged but not always confirmed as deployed.
Teams that allow an agent to run without command approval should bind that authorization to an owner, execution identity, tool set, target scope and expiration event. Logs should show who enabled the mode, the commands or tool calls made under it, and what ended the session.
Test the control with a harmless request outside an approved test directory or host. The expected result is a denied call and a policy event that identifies the rule. If the system allows the action and only records it afterward, it is auditing the boundary rather than enforcing it.