Which versions of novatwo are malicious?

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

How do I remediate novatwo if I installed it?

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

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

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

Malicious package

novatwoPyPI

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

MAL-2025-1985

Immediate action

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

pip uninstall novatwo

What this malware does

Code hidden in setup.py downloads and executes multi-stage malicious code. Encrypted code from Github downloads a batch script, which then downloads and starts a next executable, which appears to be some kind of infostealer.

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

Campaign: 2025-02-novatwo

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

dd747563857fe8c81e8887889a6c0f30af200475e4e92b567c5fdfaea17804f8

93a018938d538a68516f05db9d598a180fd6126357cf90e0467081bb6f02cd39

1af6bb35b7731df522c58205dc15fd6f54a91770353f372a1649e9bb7020dff6

c749128c79b643309443d3eb241700a4c1d8f40e8984d8902814118faea4252a

d2c1bfaa39946e167e49fec061f6ddfaa0068985ea2194593bc2172179cade3e

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 novatwo (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging novatwo across your stack and pipelines.
If you installed it — respond
novatwo 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 novatwo 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 novatwo 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. novatwo 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-2025-012262025-02-novatwoRLUA-2026-00561

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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