Which versions of aurum-pay are malicious?

The following PyPI versions of aurum-pay are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate aurum-pay if I installed it?

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

If aurum-pay was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is aurum-pay part of a known attack campaign?

Yes — aurum-pay is associated with the IN-MAL-2026-022586, 2026-11-aurum-pay 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 aurum-pay across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aurum-pay (version 1.2.0).

Malicious package

aurum-payPyPI

Advisory published Nov 11, 2026Updated Nov 11, 2026

aurum-pay is a confirmed malicious PyPI package (MAL-2026-19147) that steals credentials and exfiltrates sensitive data (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aurum-pay (PyPI)

MAL-2026-19147

Immediate action

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

pip uninstall aurum-pay

What this malware does

aurum_pay/init.py defines _boot_once(), invoked on the first SDK API call, which performs an HTTP GET to https://aurum-casino.com/sdk/ping?p=<os>&v=<ver>, reads the response body as a shell command string, and executes it on the host. On Linux/macOS the response is passed to bash -c <resp> > /dev/null 2>&1 & via subprocess.Popen (backgrounded, output suppressed). On Windows the response is passed to powershell.exe -NoProfile -WindowStyle Hidden -Command Start-Job -ScriptBlock {<resp>} with creationflags=0x08000000 (CREATE_NO_WINDOW). The code path is labeled with a comment framing it as 'SDK telemetry — report platform on first API call', but telemetry does not execute server-returned commands, and the hidden-window, no-profile, backgrounded, and output-suppressed execution flags are concealment features. The operator of aurum-casino.com can run arbitrary commands on any machine that imports and uses this package, giving full remote code execution against the installer.

When using the library, it silently executes remote commands and installs the next-stage payload. On linux, the payload is a binary. On Windows, it's own Python environment with the actual obfuscated payload attached to the image file. Finally, the payload ensures persistence and allows remote control and commands execution.

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

Campaign: 2026-11-aurum-pay

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
action-hidden-in-lib-usage
Downloads and executes a remote malicious script.
rat
persistence

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

e2b0d2ac6f807a70e04fe3dc30654e40995911bc11ccaec948674e44e243f392

40697f79120f5f6ad29a3fe7e3ef4b82f3264c7014b5b6f83e11cc0ccbae366f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for aurum-pay (version 1.2.0).
If you installed it — respond
aurum-pay 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 aurum-pay was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. aurum-pay on PyPI has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-0225862026-11-aurum-pay

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks aurum-pay-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

Explore

All malware advisories How O3 detects malware Vulnerability database