Which versions of easypydb are malicious?

The following PyPI versions of easypydb are flagged malicious: 0.4.4. Treat any of these as compromised.

How do I remediate easypydb if I installed it?

easypydb 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 easypydb — how do I know if it already compromised me?

If easypydb 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 easypydb part of a known attack campaign?

Yes — easypydb is associated with the 2024-09-old-easypydb 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 easypydb 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 easypydb (version 0.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easypydb across your stack and pipelines.

Malicious package

easypydbPyPI

Malicious code in easypydb (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12261

Immediate action

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

pip uninstall easypydb

What this malware does

The package is a wrapper around "s1db" package, which offers some kind of easy online database. However, this package silently exfiltrates credentials given by people and sends them to a Discord webhook, effectively allowing stealing data.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-09-old-easypydb

Reasons (based on the campaign):

action-hidden-in-lib-usage
exfiltration-generic

Malicious versions

1 flagged

0.4.4

Indicators of compromise (SHA-256)

177812f959194ceaf89be68acd4ee0f73f9edf00cc7c24e7748a323780e85f96

6bba8fa7c973e17898962b7fa6aebecdd0d9149b9e3a1f078bbc57f5e4bf7f0a

96f0ae7f9e01323cf16230e24267394394984c5cf3e188ed5499c86637bd0766

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 easypydb (version 0.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easypydb across your stack and pipelines.
If you installed it — respond
easypydb 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 easypydb 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 easypydb 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. easypydb on PyPI has been identified as a malicious package (version 0.4.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-09-old-easypydb

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks easypydb-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