Which versions of seclab-research-depconf-test are malicious?

The following PyPI versions of seclab-research-depconf-test are flagged malicious: 1.0, 1.1. Treat any of these as compromised.

How do I remediate seclab-research-depconf-test if I installed it?

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.

I already installed seclab-research-depconf-test — how do I know if it already compromised me?

If seclab-research-depconf-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is seclab-research-depconf-test part of a known attack campaign?

Yes — seclab-research-depconf-test is associated with the GENERIC-simple-tests 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 seclab-research-depconf-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for seclab-research-depconf-test (2 malicious versions).

Malicious package

seclab-research-depconf-testPyPI

Advisory published Jul 11, 2025Updated Dec 12, 2025

seclab-research-depconf-test is a confirmed malicious PyPI package (MAL-2025-191863) that executes malicious code on install (malicious versions 1.0, 1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in seclab-research-depconf-test (PyPI)

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

Find it
Search your lockfiles and build artifacts for seclab-research-depconf-test (2 malicious versions).
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.
Did it already run?
If seclab-research-depconf-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

bad-packages.kam193.eu

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database