Which versions of transaction-analysis are malicious?

The following PyPI versions of transaction-analysis are flagged malicious: 0.1.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate transaction-analysis if I installed it?

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

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

Yes — transaction-analysis is associated with the RLMA-2025-02009, 2025-02-coinanalyze, RLUA-2026-00835, RLUA-2026-02083 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 transaction-analysis across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for transaction-analysis (3 malicious versions).

Malicious package

transaction-analysisPyPI

Advisory published Feb 24, 2025Updated Apr 16, 2026

transaction-analysis is a confirmed malicious PyPI package (MAL-2025-3010) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in transaction-analysis (PyPI)

MAL-2025-3010

Immediate action

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

pip uninstall transaction-analysis

What this malware does

Package contains obfuscated code that exfiltrate basic data and awaits for commands from the remote server to execute them. This is a malicious copy of legitimate https://pypi.org/project/coinanalyse/ package.

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

Campaign: 2025-02-coinanalyze

Reasons (based on the campaign):

backdoor
typosquatting
obfuscation
clones-real-package
crypto-related
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

3 flagged

0.1.01.0.11.0.2

Indicators of compromise (SHA-256)

558042986b7716649a4c22caaba8a14833b810be4cec73b0a904416932da2ec4

e7136ad8929324e6882bc489519197129e477f232b9e7e4319477d9af343b451

49ab525dda997f7abc07f4ef30a62443e40a0f01e218b74d6db9b378fe51f2a4

e4a5f8f1eeaa3bb4f62fa135973916f143a5cab95f8c8d28901f9d25484e422a

7d6f0845cd5842daeae2a267876601c3aa36461b8534c852edd57d99ddc54276

625d15f5098d86371cb0781d414e737d6bf3114995c004af8b7633c606ffad0c

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2025-020092025-02-coinanalyzeRLUA-2026-00835RLUA-2026-02083

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks transaction-analysis-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