Social engineering targets aren’t always human—they can be commands, defaults, or trust assumptions baked into tools. Pgcli is a fast, interactive PostgreSQL client. It’s powerful. It rewards speed. But speed without scrutiny is where attackers slip in.
Social engineering with Pgcli can exploit workflow habits. Engineers often store connection strings in shell history or scripts. If those are shared, even briefly, credentials can leak. Pgcli supports autocompletion, which can suggest table names and columns pulled live from the database. An untrusted connection can feed poisoned metadata. That is a subtle but real vector: trust in the output can shape what you type next.
Clipboard history is another surface. Copy-paste queries with sensitive WHERE clauses or LIMIT filters can leak data into visible logs. If Pgcli scripts or history files are synced across machines, this becomes lateral movement for an attacker. Social engineering thrives on these patterns—predictable behavior, repeated shortcuts, reliance on memory caching.