Which versions of platform-harness-ecr-configmap are malicious?

The following PyPI versions of platform-harness-ecr-configmap are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate platform-harness-ecr-configmap if I installed it?

platform-harness-ecr-configmap 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 platform-harness-ecr-configmap — how do I know if it already compromised me?

If platform-harness-ecr-configmap 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 platform-harness-ecr-configmap part of a known attack campaign?

Yes — platform-harness-ecr-configmap is associated with the RLMA-2024-11116, GENERIC-standard-pypi-install-pentest, RLUA-2026-00596 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 platform-harness-ecr-configmap 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 platform-harness-ecr-configmap (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 platform-harness-ecr-configmap across your stack and pipelines.

Malicious package

platform-harness-ecr-configmapPyPI

Malicious code in platform-harness-ecr-configmap (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11659

Immediate action

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

pip uninstall platform-harness-ecr-configmap

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)

a1db276c68e96846991d60397c7fdabe14aac042ac69cc52b3e8e8d33fd56cc3

36f82912bb84a6f05561493a14a556b95b774e0538e74b3b7069ec475bb783b5

7812939dfec5496e941d5bd252e8f536d2b2e38984c285fd5881230dd705d928

6be9ddbdab95a58d013a7816684af85708d26bc1d161533aeda2f7a6c2172547

1f274f6c4f2ccee947d4f4fa97461bbb87cd9920afc3b1b8d28dbd558e2c540e

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 platform-harness-ecr-configmap (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 platform-harness-ecr-configmap across your stack and pipelines.
If you installed it — respond
platform-harness-ecr-configmap 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 platform-harness-ecr-configmap 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 platform-harness-ecr-configmap 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. platform-harness-ecr-configmap 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-11116GENERIC-standard-pypi-install-pentestRLUA-2026-00596

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks platform-harness-ecr-configmap-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