Which versions of just-test-framework are malicious?

The following PyPI versions of just-test-framework are flagged malicious: 99.99.99, 99.99.999. Treat any of these as compromised.

How do I remediate just-test-framework if I installed it?

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

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

Yes — just-test-framework is associated with the RLMA-2025-00478, 2025-01-just-framework, RLUA-2026-00444, RLUA-2026-02073 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 just-test-framework 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 just-test-framework (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging just-test-framework across your stack and pipelines.

Malicious package

just-test-frameworkPyPI

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

MAL-2025-938

Immediate action

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

pip uninstall just-test-framework

What this malware does

Importing the module exfiltrates basic information using DNS queries. There is no other purpose of the package.

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: 2025-01-just-framework

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.
dependency-confusion

Malicious versions

2 flagged

99.99.9999.99.999

Indicators of compromise (SHA-256)

15bbb124ca3fcc0bbfb96aaeb109abe698247a7e64aec19624659b7be1a7e2a4

9c346725871b0191644f4e0eba8745526f4e7f037eff29118b51bc07a03492d7

ab2d45d38003a542b3db3afaf891f8269c46e7ac1c342c06148f8859a03bc00e

14f4b5df0c5b9cb709df488e4ec2022e71f913377ec2c59e5e4eff404553cd6b

317205397255819983ed635cd71e61c23a6b096cdd25b717138c96422f44aa32

86f5277d2e2b01e1d5f24375ab47d371ddad5b5a72097dfe52b1f12e2e9dea6f

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

Campaign

RLMA-2025-004782025-01-just-frameworkRLUA-2026-00444RLUA-2026-02073

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks just-test-framework-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