Which versions of greensadway are malicious?

The following PyPI versions of greensadway are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate greensadway if I installed it?

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

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

Yes — greensadway is associated with the RLMA-2025-03610, GENERIC-standard-pypi-install-pentest, RLUA-2026-00368 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 greensadway across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for greensadway (version 0.1).

Malicious package

greensadwayPyPI

Advisory published Jul 26, 2024Updated Mar 19, 2026

greensadway is a confirmed malicious PyPI package (MAL-2025-6519) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in greensadway (PyPI)

MAL-2025-6519

Immediate action

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

pip uninstall greensadway

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

0.1

Indicators of compromise (SHA-256)

fe716e903530bacd2ccc64e7393d12f0fa9d5d1e1fa1a0869abc22c9fcd95126

6a9700b5beb781c1fa2385b4127fc981ac18e0b2a0a6779752a3b85ebf3a1486

c753b011ebd58b9c724b9078a09aa839bc2267e7828be5e90c1a33d5a4992149

97a46aef581f6d71c0a59cbddecc4c97b795929d391abf8d7ef1f097385095be

dd919c274b0f15686b442accf0e9775accc6a66b659e2dd3de30bae72d7e046b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for greensadway (version 0.1).
If you installed it — respond
greensadway 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 greensadway 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. greensadway on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03610GENERIC-standard-pypi-install-pentestRLUA-2026-00368

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks greensadway-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