Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

just4testlmPyPI

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

MAL-2026-2519
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall just4testlm

What this malware does

The package likely tests different malicious techniques and delivering payload in setup.py. Different versions, like 0.1.0, 0.4.0 or 0.9.0 contain malicious payload in setup.py that either run remote script or exfiltrate env variables during installation. The malicious versions are also quickly removed and replaced with versions without malicious code.

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

Campaign: 2026-03-just4testlm

Reasons (based on the campaign):

  • Downloads and executes a remote malicious script.

  • exfiltration-env-variables

Malicious versions

12 flagged
0.1.00.2.00.3.00.4.00.5.00.6.00.7.00.8.00.9.00.9.10.9.20.9.3

Indicators of compromise (SHA-256)

512c9983d4d153d1cf4bae9fffbddc13d5a5f58573dd4ea042dca9e43cac964b
5aed012f2ecc4af261bb7f2fc294b9aee5c0733ccf207b9e9e9a381d51387811

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for just4testlm (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging just4testlm across your stack and pipelines.

  2. If you installed it — respond

    just4testlm 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.

  3. Did it already run?

    If just4testlm 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.

  4. How O3 protects you

    O3 blocks just4testlm 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. just4testlm on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.8.0, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-questionable-pentest2026-03-just4testlm

References

Credits

  • Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks just4testlm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

just4testlm (PyPI) malicious package — MAL-2026-2519 | O3 Security