Which versions of appsec-script-py are malicious?

The following PyPI versions of appsec-script-py are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate appsec-script-py if I installed it?

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

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

Yes — appsec-script-py is associated with the RLMA-2024-10966, GENERIC-standard-pypi-install-pentest, RLUA-2026-00073 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 appsec-script-py 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 appsec-script-py (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 appsec-script-py across your stack and pipelines.

Malicious package

appsec-script-pyPyPI

Malicious code in appsec-script-py (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11523

Immediate action

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

pip uninstall appsec-script-py

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)

799f7ef6d3ceb5d6b13de6f56844c987aac05c9cb67117d254ab4fbd2d8dc7a3

3052dc3a8e561876f36be39f82eb9c0da16e1dbd04406669299dceb2ae7a9109

41394b4e398c9e82b5b97d5800a6304490350b988e3f053bb6ff9f4f0a5731f9

5a4148b7b80571ae14e46cc2f659b7476b1a5faa6c76ff95c15bd2e2969d42e8

9935eef61936a6b22eb379e8f08870d32191d368bfae96e974922b2a96c96e43

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 appsec-script-py (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 appsec-script-py across your stack and pipelines.
If you installed it — respond
appsec-script-py 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 appsec-script-py 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 appsec-script-py 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. appsec-script-py 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-10966GENERIC-standard-pypi-install-pentestRLUA-2026-00073

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks appsec-script-py-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