Which versions of managment are malicious?

The following PyPI versions of managment are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate managment if I installed it?

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

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

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

Malicious package

managmentPyPI

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

MAL-2025-6545

Immediate action

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

pip uninstall managment

What this malware does

Installing the package starts a revshell and download and starts a remote script (depending on version, different malicious functionality). The name seems to imitate CPAN.org

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

Campaign: 2025-06-cpan

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
impersonation
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

9d720922a7634b329a4b7511bf8fd3eb76fc535a18729241ad6d023abdb00bcb

d10efd77d7592101509f66a0f0f51a0442ef97129ea19356e08458254a2fc508

754c9b609bb8dafc0fd21d141cd216744d9f2aa1f23898990c52e872fdc23e1a

a8bcc6839005ea4349ecd29eeede64223cb677a5ef54db35b65f39f7957b703e

a1d1e424635535663b0fb0b245941de5908d4bf4abf1e0c391397899799cea3e

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

Campaign

RLMA-2025-036422025-06-cpanRLUA-2026-00494

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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