Which versions of testresearchpackagedc are malicious?

The following PyPI versions of testresearchpackagedc are flagged malicious: 0.1.0, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6. Treat any of these as compromised.

How do I remediate testresearchpackagedc if I installed it?

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

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

Yes — testresearchpackagedc 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 testresearchpackagedc 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 testresearchpackagedc (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testresearchpackagedc across your stack and pipelines.

Malicious package

testresearchpackagedcPyPI

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

MAL-2025-1512

Immediate action

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

pip uninstall testresearchpackagedc

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.

The OpenSSF Package Analysis project identified 'testresearchpackagedc' @ 0.1.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

6 flagged

0.1.00.1.20.1.30.1.40.1.50.1.6

Indicators of compromise (SHA-256)

cb6e63a51de79ba3f21f381f82a4f17b1b9627c51173ea1ee6482929813b0511

93f70e79a91cdc433890cbb2af2356854c11d23ae7255e7d2e5abdfbc8b45fbc

b9a3d67880a7182900acdd5dafdb79bff126438c5538693dbd27c0c0848b2fb3

222c9aab133960ef3a9bc2b06322e8631c93e736b5983572730387ffc09ceae2

c5c4116e65563422a5bfc464d57acdfb88b55d91e4024fcd766b6d82ad0e090d

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 testresearchpackagedc (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testresearchpackagedc across your stack and pipelines.
If you installed it — respond
testresearchpackagedc 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 testresearchpackagedc 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 testresearchpackagedc 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. testresearchpackagedc on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6 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)
OpenSSF: Package Analysis · finder

Detect & block this

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