Which versions of amzn-sagemaker-studio are malicious?

The following PyPI versions of amzn-sagemaker-studio are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate amzn-sagemaker-studio if I installed it?

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

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

Yes — amzn-sagemaker-studio is associated with the 2025-09-amzn-sagemaker-studio 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 amzn-sagemaker-studio 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 amzn-sagemaker-studio (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amzn-sagemaker-studio across your stack and pipelines.

Malicious package

amzn-sagemaker-studioPyPI

Malicious code in amzn-sagemaker-studio (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191680

Immediate action

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

pip uninstall amzn-sagemaker-studio

What this malware does

Package exfiltrates the environment variables during the import

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

Campaign: 2025-09-amzn-sagemaker-studio

Reasons (based on the campaign):

exfiltration-env-variables
dependency-confusion

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

36c198a080b9cee5e67f0b4d799ba2de868fdf4619fe4fcf1a2088a3972d9ace

a557d275cca7627fa4d3e2c72f0fc9b78fc5ac70aa87a0ab586f1abf9f8777a6

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

Campaign

2025-09-amzn-sagemaker-studio

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks amzn-sagemaker-studio-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