Which versions of pacakegenow are malicious?

The following PyPI versions of pacakegenow are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate pacakegenow if I installed it?

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

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

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

Malicious package

pacakegenowPyPI

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

MAL-2025-47793

Immediate action

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

pip uninstall pacakegenow

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

3842b4c32f6d90da97d97f76daeb74de9a173f53e7c96e3811f9fc8599e6ccdd

e2618f07e689302ef37bdd76e313dc87047919b9f248c20a87e607830c46da83

4e6e546396a62564e76e758bc338b07b8567b32dce9f89bdf5a59d3a670eedc9

8cb1e18361856688f0eec9b56f4989a02a1c43414a0002f2d05a4310bb145add

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

Campaign

RLMA-2025-047982025-08-k7eelRLUA-2026-00578

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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