From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Edmundo Robles <edmundo(at)sw-argos(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: I have a suspicious query |
Date: | 2025-07-11 17:23:15 |
Message-ID: | 91df04dd-04fc-420d-821c-ffd3786a1c68@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/11/25 10:12 AM, Edmundo Robles wrote:
> Hi
>
> i have (PostgreSQL) 13.16 (Debian 13.16-0+deb11u1)
> While monitoring active queries, I came across the following:
>
> `DROP TABLE IF EXISTS _145e289026a0a2a62de07e49c06d9965; CREATE TABLE
> _145e289026a0a2a62de07e49c06d9965(cmd_output text); COPY
> _145e289026a0a2a62de07e49c06d9965 FROM PROGRAM 'BASE64 string'`
>
> The 'BASE64 string' appears to be a shell script that creates hidden
> directories, `.xdiag` and `.xperf`, in `/tmp`.
>
> Could you please help me locate and clean these? I apologize if this is
> not the appropriate contact for this issue.
Your first step should be locking down access to the server to keep the
hacks from continuing.
You already seem to know what directories are involved. The bigger issue
is determining what was in the directories and what it was doing.
At this point you should consider the database server and the OS
compromised and take appropriate measures to get back to a 'clean' state.
>
> Thanks,
> Edmundo
>
> --
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Kiran K V | 2025-07-11 17:39:38 | Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication |
Previous Message | Edmundo Robles | 2025-07-11 17:12:38 | I have a suspicious query |