Which versions of netpackat are malicious?

The following PyPI versions of netpackat are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate netpackat if I installed it?

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

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

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

Malicious package

netpackatPyPI

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

MAL-2025-5120

Immediate action

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

pip uninstall netpackat

What this malware does

Code download and runs an executable, which is widely recognized as malware. The system is also configured to run it on startup, and the file is saved in paths attempting to look as a system file.

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

Campaign: 2025-05-requestpackat

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware
peristence-autorun

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

364bc6883ac08ccaa71c86fbd4ddea8c088ae2724d571bffab75d896ea1b9277

fca30f947fe155b7e74e8f753caff8d20377ff4090a95512595c7bdc413266db

f0f971eaa8aa4f59d981802034020fcd9b7c6008c2e9ed41a868a9e3186e7eed

4d00cb14bddfeac7255045a34f499cbe51fcf96a229ab60e5f4fb69d3cd5b745

289b33921d587bd0778af30e88dffd763cd67b419524fdb81cdb67e3f25a113f

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

Campaign

RLMA-2025-030172025-05-requestpackatRLUA-2026-00553

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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