Which versions of pckaging are malicious?

The following PyPI versions of pckaging are flagged malicious: 0.3. Treat any of these as compromised.

How do I remediate pckaging if I installed it?

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

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

Yes — pckaging is associated with the RLMA-2024-11111, GENERIC-standard-pypi-install-pentest, RLUA-2026-00583 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 pckaging 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 pckaging (version 0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pckaging across your stack and pipelines.

Malicious package

pckagingPyPI

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

MAL-2024-11655

Immediate action

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

pip uninstall pckaging

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.3

Indicators of compromise (SHA-256)

2461e29e9edaf24956f44e2901c32cbed8105766f3fa2a95b3b63270ded95583

7a3cb0261412ccb8aa3b373e25bba261da48de3b11f28192de8bf36194e4c942

22d95e82784e0b931da5081722f930a6c3acedcaec6688e70859941b9f2963f4

f959c1ec877a42f40146857832e3ec5a5e5c4089457c99b38fb1ef1004632550

3546769f88fe021224111ba7d536f77ecdd77701ccefa198bc0b03579411aacc

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

Campaign

RLMA-2024-11111GENERIC-standard-pypi-install-pentestRLUA-2026-00583

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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