Which versions of postgresql-connector-python are malicious?

The following PyPI versions of postgresql-connector-python are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate postgresql-connector-python if I installed it?

postgresql-connector-python is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed postgresql-connector-python — how do I know if it already compromised me?

If postgresql-connector-python was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is postgresql-connector-python part of a known attack campaign?

Yes — postgresql-connector-python is associated with the GENERIC-standard-pypi-install-pentest campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find postgresql-connector-python across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for postgresql-connector-python (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging postgresql-connector-python across your stack and pipelines.

Malicious package

postgresql-connector-pythonPyPI

Malicious code in postgresql-connector-python (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12328

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall postgresql-connector-python

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4847c471468eb2c2e0b8120aa704a619c6d027d2f50ee636f168dc0d9e048059

87f55ac62324b5fc631b711e125f897d8ae10d06a9d80173463d9a5fa1915302

b36366cbc65a0e7a341c06b1bf8866dfe6fb9f9d87d3d1594a0d6093c7bf1ce5

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for postgresql-connector-python (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging postgresql-connector-python across your stack and pipelines.
If you installed it — respond
postgresql-connector-python is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If postgresql-connector-python was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks postgresql-connector-python before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. postgresql-connector-python on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks postgresql-connector-python-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring