mal-2025-191909
Vulnerability from ossf_malicious_packages
Published
2025-02-21 21:50
Modified
2025-12-31 02:45
Summary
Malicious code in transaction-utils (PyPI)
Details
-= Per source details. Do not edit below this line.=-
Source: kam193 (c1efc9cf33a18e7f3c4294c39aabadf136974e4e2ee56c874ba337ac609c6b77)
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.
Credits
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "transaction-utils"
},
"versions": [
"0.1.1",
"0.1"
]
}
],
"credits": [
{
"contact": [
"https://github.com/kam193",
"https://bad-packages.kam193.eu/"
],
"name": "Kamil Ma\u0144kowski (kam193)"
},
{
"contact": [
"https://github.com/kam193",
"https://bad-packages.kam193.eu/"
],
"name": "Kamil Ma\u0144kowski (kam193)",
"type": "REPORTER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "pypi/2025-02-transaction-utils/transaction-utils",
"import_time": "2025-12-02T22:30:55.658060024Z",
"modified_time": "2025-02-21T21:50:10Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"sha256": "5fe7c88b0f2c7b577871f1cbf57dea7dafafbe8f49ed614fe91045ae46986353",
"source": "kam193"
},
{
"id": "pypi/2025-02-transaction-utils/transaction-utils",
"import_time": "2025-12-02T23:07:18.701665029Z",
"modified_time": "2025-02-21T21:50:10Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"sha256": "c1efc9cf33a18e7f3c4294c39aabadf136974e4e2ee56c874ba337ac609c6b77",
"source": "kam193"
},
{
"id": "pypi/2025-02-transaction-utils/transaction-utils",
"import_time": "2025-12-10T21:38:57.886762331Z",
"modified_time": "2025-02-21T21:50:10Z",
"sha256": "1b1fd665949fe7b8145ab0c6aeb26c6950171b4ca1e449d9ba8eda9227e6c7ae",
"source": "kam193",
"versions": [
"0.1.1",
"0.1"
]
},
{
"id": "pypi/2025-02-transaction-utils/transaction-utils",
"import_time": "2025-12-30T22:39:04.199269464Z",
"modified_time": "2025-02-21T21:50:10Z",
"sha256": "2a0fde628104dfcff959e7931714a1c5868630a2aa2f47c88ffc3b2cdc83cc31",
"source": "kam193",
"versions": [
"0.1",
"0.1.1"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: kam193 (c1efc9cf33a18e7f3c4294c39aabadf136974e4e2ee56c874ba337ac609c6b77)\nThe only thing the package does is send out all the given data about a cryptocurrency transaction, including the private key, to a hardcoded webhook.\n\nFeedback 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.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2025-02-transaction-utils\n\n\nReasons (based on the campaign):\n\n\n - crypto-related\n\n\n - action-hidden-in-lib-usage\n\n\n - A Telegram webhook is used to send collected data.\n",
"id": "MAL-2025-191909",
"modified": "2025-12-31T02:45:16Z",
"published": "2025-02-21T21:50:10Z",
"references": [
{
"type": "WEB",
"url": "https://bad-packages.kam193.eu/pypi/package/transaction-utils"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in transaction-utils (PyPI)"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…