Which versions of test128123612 are malicious?

The following PyPI versions of test128123612 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate test128123612 if I installed it?

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

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

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

Malicious package

test128123612PyPI

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

MAL-2024-11723

Immediate action

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

pip uninstall test128123612

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

a70afc318fe78fb6c45b531fb29426ef1c9bfaac0b75601ed83c63ca32f6a2af

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test128123612 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test128123612 across your stack and pipelines.
If you installed it — respond
Remove test128123612 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 test128123612 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 test128123612 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. test128123612 on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11182

Credits

ReversingLabs · finder

Detect & block this

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

test128123612PyPI

Malicious versions

Indicators of compromise (SHA-256)

Detection & response playbook

Find it

If you installed it — respond

Did it already run?

How O3 protects you

Frequently asked questions

Campaign

Credits

Detect & block this