Which versions of formatter-test-package are malicious?

The following PyPI versions of formatter-test-package are flagged malicious: 0.0.1, 0.0.2, 0.1.0, 0.1.2, 0.1.3, 0.1.4, 0.1.7, 0.1.8, 0.1.9, 0.1.10, 0.1.11. Treat any of these as compromised.

How do I remediate formatter-test-package if I installed it?

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

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

Yes — formatter-test-package is associated with the RLMA-2024-08295, RLUA-2024-11048, 2024-08-moti-analytics, RLUA-2026-00332 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 formatter-test-package 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 formatter-test-package (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging formatter-test-package across your stack and pipelines.

Malicious package

formatter-test-packagePyPI

Malicious code in formatter-test-package (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10029

Immediate action

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

pip uninstall formatter-test-package

What this malware does

The package is designed to exfiltrate basic data, like hostname and OS details, as well as collect information about the stacktrace it's imported from.

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: 2024-08-moti-analytics

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.

Malicious versions

11 flagged

0.0.10.0.20.1.00.1.20.1.30.1.40.1.70.1.80.1.90.1.100.1.11

Indicators of compromise (SHA-256)

2f1e8ecc1c090422f298f22a1465dc4b301c3276f12d3b233e89b78d6c1191f1

4712e8eb7f6922aafa564be28e9952f4b3defab9333199f3c240b4ecfdfc7961

26e8ed347a69840b73c532b164570f913a31ba3cf41b4b8317ddcefbb30a5d74

8ad808b5e90e246a93704f922e2dd59bf4c5954fdfc55ccf5371c6b13ac7483f

b85e0e20ec2c61234005b7005df588ba13122e59df55417f4b6de82d36a7c749

8fe656cecfe48b2d3076b02460ea417fa59ee90901c61f83a84cc25df3f8a424

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 formatter-test-package (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging formatter-test-package across your stack and pipelines.
If you installed it — respond
formatter-test-package 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 formatter-test-package 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 formatter-test-package 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. formatter-test-package on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.1.0, 0.1.2, 0.1.3, 0.1.4, 0.1.7, 0.1.8, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-08295RLUA-2024-110482024-08-moti-analyticsRLUA-2026-00332

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks formatter-test-package-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