Which versions of justanything are malicious?

The following PyPI versions of justanything are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate justanything if I installed it?

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

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

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

Malicious package

justanythingPyPI

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

MAL-2025-6531

Immediate action

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

pip uninstall justanything

What this malware does

Code is designed to download and run remote scripts during installation, which finally downloads and starts an infostealer

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

Campaign: 2025-06-justanything

Reasons (based on the campaign):

infostealer
The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote malicious script.
Downloads and executes a remote executable.

Malicious versions

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

a9aa75c187e72700ba09ed4702cffa378cadeb41eeb75d23c948f482db23d958

5e1f94487dbebd32a85316b803acaa36b561736cb623779bfb16230740d6d4a7

206471fdab67d7afeeb5fa6ee55cdb14b88338b58b50a5b73f31bbbb5e66e65b

36d8d08634f081e7ca5a41a775e7df4da0ff4eee88614636be798a2180e74b25

cd665efafa85a40cabfc8646ae2c697e6563c527618cc6560a95a5034063ca42

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

Campaign

RLMA-2025-036242025-06-justanythingRLUA-2026-00445

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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