Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

seclab-research-depconf-testPyPI

Malicious code in seclab-research-depconf-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191863
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall seclab-research-depconf-test

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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-simple-tests

Reasons (based on the campaign):

  • The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged
1.01.1

Indicators of compromise (SHA-256)

ff6438b5d317eada3573f7004e6fe020c614a6ef78dd2f3368af6cff0c66d567
71ecf56c682dd44134d9a4d17fb2ae3d20091681372f89902c84d5dc2533c03d
652a970ac15105d4e0f77f9d72e0266ce26807df0196f3e28e48fb7bb7b329db

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove seclab-research-depconf-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If seclab-research-depconf-test 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.

  4. How O3 protects you

    O3 blocks seclab-research-depconf-test 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. seclab-research-depconf-test on PyPI has been identified as a malicious package (versions 1.0, 1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

O3 blocks seclab-research-depconf-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

seclab-research-depconf-test (PyPI) malicious package — MAL-2025-191863 | O3 Security