{"vulnerability": "cve-2024-5291", "sightings": [{"uuid": "122b9559-3523-4633-aa3b-c64500ff7216", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52912", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501822996333543", "content": "", "creation_timestamp": "2024-11-18T03:26:15.911839Z"}, {"uuid": "bc547374-32d6-4e9b-bccd-ddcc9de07922", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52913", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501823010069406", "content": "", "creation_timestamp": "2024-11-18T03:26:16.036184Z"}, {"uuid": "a5201675-f143-4433-b304-dc6ddc7bf05e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52914", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501895271876776", "content": "", "creation_timestamp": "2024-11-18T03:44:38.633659Z"}, {"uuid": "6cfb996b-d21e-4ca2-b972-e36ebdf2f812", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52915", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501895287297127", "content": "", "creation_timestamp": "2024-11-18T03:44:39.046811Z"}, {"uuid": "d8fa4351-7e4f-43fb-b25f-a2b81ee72935", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52916", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501895302295337", "content": "", "creation_timestamp": "2024-11-18T03:44:39.233309Z"}, {"uuid": "80ff3529-bc47-419d-8a10-1bd58e63d17c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52912", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501836223807235", "content": "", "creation_timestamp": "2024-11-18T03:29:39.157522Z"}, {"uuid": "92ccd6b0-6a54-42c5-9d7e-b4245eab9edf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52913", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501836237633076", "content": "", "creation_timestamp": "2024-11-18T03:29:40.094061Z"}, {"uuid": "6adaba0e-8714-443a-b6f4-27d1658238de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52917", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501895335597940", "content": "", "creation_timestamp": "2024-11-18T03:44:39.822530Z"}, {"uuid": "302a8e0c-3325-4046-9acd-539b81f4d4ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52918", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501954333981684", "content": "", "creation_timestamp": "2024-11-18T03:59:39.822572Z"}, {"uuid": "0f7549d3-744a-4964-9591-845e48da2f7f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52919", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113501954348301101", "content": "", "creation_timestamp": "2024-11-18T03:59:40.349003Z"}, {"uuid": "e7ccf34b-2ddf-4d30-b1ec-00b055ead325", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52913", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113620042624297259", "content": "", "creation_timestamp": "2024-12-09T00:31:04.069650Z"}, {"uuid": "ae635c6c-a22d-4927-8084-306834ad7310", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52913", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/6460", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-55563\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: Bitcoin Core through 27.2 allows transaction-relay jamming via an off-chain protocol attack, a related issue to CVE-2024-52913. For example, the outcome of an HTLC (Hashed Timelock Contract) can be changed because a flood of transaction traffic prevents propagation of certain Lightning channel transactions.\n\ud83d\udccf Published: 2024-12-09T00:00:00.000Z\n\ud83d\udccf Modified: 2025-03-04T21:33:22.130Z\n\ud83d\udd17 References:\n1. https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures\n2. https://bitcoincore.org\n3. https://delvingbitcoin.org/t/full-disclosure-transaction-relay-throughput-overflow-attacks-against-off-chain-protocols/1305\n4. https://gnusha.org/pi/bitcoindev/CALZpt+EptER=p+P7VN3QAb9n=dODA9_LnR9xZwWpRsdAwedv=w@mail.gmail.com/T/#u\n5. https://ariard.github.io", "creation_timestamp": "2025-03-04T22:33:34.000000Z"}, {"uuid": "211191a7-e53f-4a5e-9f43-c187cab1e432", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52915", "type": "seen", "source": "https://bsky.app/profile/2rZiKKbOU3nTafniR2qMMSE0gwZ.activitypub.awakari.com.ap.brid.gy/post/3lyprvcqcrh32", "content": "", "creation_timestamp": "2025-09-13T12:35:17.272682Z"}, {"uuid": "3d116db5-e7ec-4809-a19c-0c315f0099b7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/blockchainreport.bsky.social/post/3ml4csxovlk2j", "content": "Critical #Bitcoin Core vulnerability (CVE-2024-52911) found in versions 0.14.0-29.0. Specially crafted blocks could cause remote node crashes or potential code execution by exploiting a memory error during transaction validation. Monitor official Bitcoin Core channels for patches. #crypto #security", "creation_timestamp": "2026-05-05T13:40:48.983397Z"}, {"uuid": "ddfc0406-2be9-402c-9a03-29cc3fd96ee4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52913", "type": "seen", "source": "https://t.me/cvedetector/12341", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-55563 - Bitcoin Core Transaction Relay Jamming Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-55563 \nPublished : Dec. 9, 2024, 1:15 a.m. | 1\u00a0hour, 8\u00a0minutes ago \nDescription : Bitcoin Core through 27.2 allows transaction-relay jamming via an off-chain protocol attack, a related issue to CVE-2024-52913. For example, the outcome of an HTLC (Hashed Timelock Contract) can be changed because a flood of transaction traffic prevents propagation of certain Lightning channel transactions. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-09T03:49:17.000000Z"}, {"uuid": "440befbf-32f7-4d5a-815d-11b03a6fdb26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52919", "type": "seen", "source": "https://t.me/cvedetector/11274", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52919 - Bitcoin Core CAddrMan Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-52919 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:26.000000Z"}, {"uuid": "9fac6ab5-096e-4e02-bc91-f67fb46e9c65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52918", "type": "seen", "source": "https://t.me/cvedetector/11273", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52918 - Bitcoin Core Memory Consumption Denial of Service\", \n  \"Content\": \"CVE ID : CVE-2024-52918 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : Bitcoin-Qt in Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption and application crash) via a BIP21 r parameter for a URL that has a large file. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:23.000000Z"}, {"uuid": "06f91ed3-9a1d-4a18-a516-41bf8fbb9314", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52917", "type": "seen", "source": "https://t.me/cvedetector/11272", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52917 - Bitcoin Core Uncontrolled Memory Allocation in miniupnp Leading to DOS\", \n  \"Content\": \"CVE ID : CVE-2024-52917 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : Bitcoin Core before 22.0 has a miniupnp infinite loop in which it allocates memory on the basis of random data received over the network, e.g., large M-SEARCH replies from a fake UPnP device. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:22.000000Z"}, {"uuid": "95c6caef-ac25-4836-a01b-19039b6f75db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52916", "type": "seen", "source": "https://t.me/cvedetector/11271", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52916 - Bitcoin Core Denial of Service Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-52916 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:21.000000Z"}, {"uuid": "9c002ef8-e697-4cbc-b649-4d63b21520c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52915", "type": "seen", "source": "https://t.me/cvedetector/11270", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52915 - Bitcoin Core Remote Denial of Service\", \n  \"Content\": \"CVE ID : CVE-2024-52915 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:20.000000Z"}, {"uuid": "cbb869ca-f568-4ddb-a60a-361ad647598c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52914", "type": "seen", "source": "https://t.me/cvedetector/11269", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52914 - Bitcoin Core Denial of Service (DoS)\", \n  \"Content\": \"CVE ID : CVE-2024-52914 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:19.000000Z"}, {"uuid": "045b18b6-5d82-4e02-aa98-7bbbc6bdd8ef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52913", "type": "seen", "source": "https://t.me/cvedetector/11268", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52913 - Bitcoin Core Transaction Disabling Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-52913 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:15.000000Z"}, {"uuid": "78527d9c-7a15-4f29-b3a9-110ca23f15e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52912", "type": "seen", "source": "https://t.me/cvedetector/11267", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-52912 - Bitcoin Core Integer Overflow and Logic Bug Network Split\", \n  \"Content\": \"CVE ID : CVE-2024-52912 \nPublished : Nov. 18, 2024, 4:15 a.m. | 24\u00a0minutes ago \nDescription : Bitcoin Core before 0.21.0 allows a network split that is resultant from an integer overflow (calculating the time offset for newly connecting peers) and an abs64 logic bug. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"18 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-18T05:40:14.000000Z"}, {"uuid": "1aa60b22-7de6-4e77-9fe6-c652ec164e62", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/codelogic00.bsky.social/post/3ml6d5ugjtn2s", "content": "Bitcoin Core reveals a bug that could allow miners to crash\u00a0nodes\n\nBitcoin Core developers have revealed a high-risk bug that could allow miners to crash some Bitcoin nodes remotely. summary Bitcoin Core has disclosed CVE-2024-52911, affecting versions before 29.0, with older nodes still exposed\u2026", "creation_timestamp": "2026-05-06T08:52:14.056614Z"}, {"uuid": "4fe68e14-2c10-4b4e-8826-7344cde74548", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/cryptoeconomy.bsky.social/post/3ml7fejsljs2y", "content": "\ud83d\udea8 Bitcoin Core Fixes Critical Bug\n\nBitcoin Core quietly fixed CVE-2024-52911, a memory flaw affecting versions 0.14.0 to 28.x that still leaves outdated nodes exposed.\n\n#Bitcoin #BitcoinCore #BTC #Cybersecurity #Crypto", "creation_timestamp": "2026-05-06T19:04:59.343479Z"}, {"uuid": "afbc7528-aff0-40db-8055-b1ee736b6178", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/bitnewsbot.bsky.social/post/3ml56fu23vq2p", "content": "A critical memory safety vulnerability (CVE-2024-52911) in Bitcoin Core software versions 0.14.1 through 28.4 allowed miners to crash nodes or [\u2026]", "creation_timestamp": "2026-05-05T21:54:33.966329Z"}, {"uuid": "e5022e5e-fd38-422f-aec0-2abffb16fd91", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/cryptonews-poster.bsky.social/post/3ml5momb6cx2m", "content": "CRITICAL Bitcoin Core vulnerability (CVE-2024-52911) in versions 0.14.1-28.4 allows remote code execution/crashes. Discovered Nov '24, patched Dec '24. Yet, ~43% nodes vulnerable! Exploit is costly (high hash power), but risk remains. Upgrade ASAP!\n\n#crypto #blockchain #news ", "creation_timestamp": "2026-05-06T02:09:59.738071Z"}, {"uuid": "d292d2a9-6e14-4ff5-a109-07846d28a011", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/cryptovka-news.bsky.social/post/3ml5mpmjghk2m", "content": "\ud83d\udea8 Bitcoin Core Vulnerability CVE-2024-52911: 43% of nodes remain unpatched, risking crashes & remote code execution. Versions 0.14.1-28.4 affected. Exploitation needs high hash power, but updates are vital. #Bitcoin #Security #CVE", "creation_timestamp": "2026-05-06T02:10:36.744174Z"}, {"uuid": "76512236-c7ca-41f4-a606-bc3f6bf2c66d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-52911", "type": "seen", "source": "https://bsky.app/profile/news.cryptovka.ru/post/3ml5ms7ycgk2b", "content": "\ud83d\udd25 \u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c CVE-2024-52911 \u0432 Bitcoin Core! \u26a0\ufe0f \u041e\u043a\u043e\u043b\u043e 43% \u0443\u0437\u043b\u043e\u0432 \u043e\u0441\u0442\u0430\u044e\u0442\u0441\u044f \u043f\u043e\u0434 \u0443\u0433\u0440\u043e\u0437\u043e\u0439 \u0441\u0431\u043e\u0435\u0432 \u0438 RCE. \u0420\u0435\u043a\u043e\u043c\u0435\u043d\u0434\u0443\u0435\u0442\u0441\u044f \u0441\u0440\u043e\u0447\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0434\u043e v29+ \u0434\u043b\u044f \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0441\u0435\u0442\u0438. #Bitcoin #CryptoNews #Blockchain", "creation_timestamp": "2026-05-06T02:12:02.615660Z"}]}