Which versions of better-gradient are malicious?

The following PyPI versions of better-gradient are flagged malicious: 0.1.0, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate better-gradient if I installed it?

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

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

Yes — better-gradient is associated with the RLMA-2024-07853, duvet-love-odyssey, RLUA-2026-00143 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 better-gradient across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for better-gradient (3 malicious versions).

Malicious package

better-gradientPyPI

Advisory published Jul 6, 2024Updated Mar 19, 2026

better-gradient is a confirmed malicious PyPI package (MAL-2024-9949) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0, 0.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in better-gradient (PyPI)

MAL-2024-9949

Immediate action

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

pip uninstall better-gradient

What this malware does

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

Campaign: duvet-love-odyssey

Reasons (based on the campaign):

infostealer

Malicious versions

3 flagged

0.1.00.2.00.3.0

Indicators of compromise (SHA-256)

7dc087be48c952db5cca91dd64c58afcbc6d152d30af7ae207aba963b0e8f0a3

a398c3571e3e71645540232cba3b7c7d33b44ca067b85db83814ba231d48593b

61ee3d2a1011f83d233eed4719b397bc9a4e69c449841335b187b323d9f980fc

a7c3d0f466e2586ba5c9c9041ab48d9282457df20bbc3e7a8db068ed0c8c8bc0

cf5e3b1c0ece4feb9390ca338b9a84f4b6f70bc1f75402ec61355a8361851e78

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2024-07853duvet-love-odysseyRLUA-2026-00143

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks better-gradient-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