Which versions of security-automation-job are malicious?

The following PyPI versions of security-automation-job are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate security-automation-job if I installed it?

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

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

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

Malicious package

security-automation-jobPyPI

Malicious code in security-automation-job (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11703

Immediate action

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

pip uninstall security-automation-job

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

99.99.99

Indicators of compromise (SHA-256)

14e26fe3dedc48d3007daa33e9c6bb7c418033294a1382f3b22e7e728bb19541

cef6944bd98b07b352cb061b3f554da61bc4620ed6d21caf97d8ab484cf26c92

38eb272538ac306cb26b84b3887bf6fd77f00fe00e64a10814f34258702eb442

f20204a3adde46d981eb163dc8c43940e826b244deeb4fd76d1cc5320e120511

f2a281d774cd4dc33754ccc59ef5eaf977170aabf389ecfdc42823b42c4f55fa

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

Campaign

RLMA-2024-11161GENERIC-standard-pypi-install-pentestRLUA-2026-00749

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks security-automation-job-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