Which versions of transaction-utils are malicious?

The following PyPI versions of transaction-utils are flagged malicious: 0.1, 0.1.1. Treat any of these as compromised.

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

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

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

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

Malicious package

transaction-utilsPyPI

Malicious code in transaction-utils (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191909

Immediate action

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

pip uninstall transaction-utils

What this malware does

The only thing the package does is send out all the given data about a cryptocurrency transaction, including the private key, to a hardcoded webhook.

Feedback from PyPI Team: the package "transaction-utils" may also exploit a known pip behavior to overwrite files of an existing legitime package and replace it with malicious content.

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

Campaign: 2025-02-transaction-utils

Reasons (based on the campaign):

crypto-related
action-hidden-in-lib-usage
A Telegram webhook is used to send collected data.

Malicious versions

2 flagged

0.10.1.1

Indicators of compromise (SHA-256)

5fe7c88b0f2c7b577871f1cbf57dea7dafafbe8f49ed614fe91045ae46986353

c1efc9cf33a18e7f3c4294c39aabadf136974e4e2ee56c874ba337ac609c6b77

1b1fd665949fe7b8145ab0c6aeb26c6950171b4ca1e449d9ba8eda9227e6c7ae

2a0fde628104dfcff959e7931714a1c5868630a2aa2f47c88ffc3b2cdc83cc31

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

Campaign

2025-02-transaction-utils

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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