Which versions of thisismytest are malicious?

The following PyPI versions of thisismytest are flagged malicious: 1.0.0, 2.0.0, 3.0.0, 4.0.0, 5.0.0. Treat any of these as compromised.

How do I remediate thisismytest if I installed it?

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

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

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

Malicious package

thisismytestPyPI

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

MAL-2026-2017

Immediate action

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

pip uninstall thisismytest

What this malware does

During installation, the package downloads and runs a remote executable, which is identified as a backdoor. It connects with a remote server and executes basic commands

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

Campaign: 2026-03-thisismytest

Reasons (based on the campaign):

malware
Downloads and executes a remote executable.
backdoor

The OpenSSF Package Analysis project identified 'thisismytest' @ 4.0.0 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

5 flagged

1.0.02.0.03.0.04.0.05.0.0

Indicators of compromise (SHA-256)

a1c269bbb834081025da993697e3e2e44db4a97e16e21f4c792ed85391772fa9

19f3b6e447fea825bca111985cb5f707015439b58f5d4982bb33b91a8f37a1c0

421d783dd1f7d99fd582b5a07e9f691a9c568faa36be4595a167fc98a6c3334e

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

Campaign

2026-03-thisismytest

References

Credits

Kamil Mańkowski (kam193) · reporter
OpenSSF: Package Analysis · finder

Detect & block this

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