What does the thisismytest123 malware do?

During installation, if run under a specific username, the package downloads and installs two executables identified as backdoors trojans. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-03-thisismytest123 Reasons (based on the campaign): - Downloads and executes a remote executable. - backdoor - malware The OpenSSF Package Analysis project identified 'thisismytest123' @ 1.0.0 (pypi) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of thisismytest123 are malicious?

The following PyPI versions of thisismytest123 are flagged malicious: 1.0.0, 2.0.0. Treat any of these as compromised.

How do I remediate thisismytest123 if I installed it?

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

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

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

Malicious package

thisismytest123PyPI

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

MAL-2026-2255

Immediate action

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

pip uninstall thisismytest123

What this malware does

During installation, if run under a specific username, the package downloads and installs two executables identified as backdoors trojans.

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

Campaign: 2026-03-thisismytest123

Reasons (based on the campaign):

Downloads and executes a remote executable.
backdoor
malware

The OpenSSF Package Analysis project identified 'thisismytest123' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged

1.0.02.0.0

Indicators of compromise (SHA-256)

7587966a3d79cfe783b06cfea4893cd3d3c445d8c1783c81d4b1ff797e591141

c1564ec3a6b1a2fee0aacfbeafde84cba8e249a9294b771f43610ff371942a6d

7640ee5ded7bcafbd9863565d68a7768bdc9bd2abca56a69d73576e7e9b2c0df

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

Campaign

2026-03-thisismytest123

References

Credits

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

Detect & block this

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