<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>International Money Flow</title><description>Curated security advisories and detection engineering for financial infrastructure. We track, verify, and republish vulnerabilities relevant to payments, settlement, and treasury operations.</description><link>https://imfamericas.com/</link><language>en</language><item><title>[Advisory · CRITICAL] Backdoor in xz-utils 5.6.0–5.6.1 (liblzma) compromises sshd</title><link>https://imfamericas.com/advisories/2024-03-29-cve-2024-3094-xz-utils-backdoor/</link><guid isPermaLink="true">https://imfamericas.com/advisories/2024-03-29-cve-2024-3094-xz-utils-backdoor/</guid><description>xz-utils 5.6.0 and 5.6.1 ship a deliberate backdoor that compromises sshd via the libsystemd → liblzma load path. An attacker holding the actor&apos;s private key gains pre-authentication RCE as root.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><category>advisory</category><category>critical</category><category>CVE-2024-3094</category></item><item><title>[Advisory · MEDIUM] Envoy HTTP/2 CONTINUATION frame flood causes CPU exhaustion DoS</title><link>https://imfamericas.com/advisories/2024-04-03-cve-2024-30255-envoy-http2-continuation-flood/</link><guid isPermaLink="true">https://imfamericas.com/advisories/2024-04-03-cve-2024-30255-envoy-http2-continuation-flood/</guid><description>Envoy&apos;s HTTP/2 codec processes CONTINUATION frames without effective rate limiting. A remote unauthenticated client can stream CONTINUATION frames indefinitely, exhausting CPU on the target. Part of the wider 2024 HTTP/2 CONTINUATION flood disclosure class.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><category>advisory</category><category>medium</category><category>CVE-2024-30255</category></item><item><title>[Advisory · HIGH] Signal handler race in OpenSSH sshd allows pre-auth RCE on glibc Linux</title><link>https://imfamericas.com/advisories/2024-07-01-cve-2024-6387-openssh-regresshion/</link><guid isPermaLink="true">https://imfamericas.com/advisories/2024-07-01-cve-2024-6387-openssh-regresshion/</guid><description>A signal handler race condition in sshd, dubbed regreSSHion, permits unauthenticated remote code execution as root on glibc-based Linux. The flaw is a regression of CVE-2006-5051. Exploitation is non-trivial but demonstrated.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><category>advisory</category><category>high</category><category>CVE-2024-6387</category></item><item><title>[Paper] Adversarial attacks against machine-learning systems in financial services</title><link>https://imfamericas.com/papers/2026-04-29-adversarial-attacks-against-financial-ml/</link><guid isPermaLink="true">https://imfamericas.com/papers/2026-04-29-adversarial-attacks-against-financial-ml/</guid><description>Financial institutions are deploying ML systems into the parts of their stack that matter most: fraud detection, anti-money-laundering screening, credit decisioning, transaction monitoring, and customer-service LLMs. These systems carry an attack surface that traditional cyber-security controls do not address. This paper defines six adversarial attack classes specific to financial-sector ML, maps them to malicious-actor goals, and proposes a starting threat model for the institutions we work with.</description><pubDate>Wed, 29 Apr 2026 00:00:00 GMT</pubDate><category>paper</category><category>analysis</category><category>adversarial-machine-learning</category><category>fraud-detection</category><category>aml-kyc</category><category>transaction-monitoring</category><category>llm-security</category></item><item><title>[Paper] Could your choice of payment-fraud telemetry be harming your detection?</title><link>https://imfamericas.com/papers/2026-04-22-payment-fraud-telemetry-bad-metrics/</link><guid isPermaLink="true">https://imfamericas.com/papers/2026-04-22-payment-fraud-telemetry-bad-metrics/</guid><description>Most fraud-detection programmes report on the wrong things. Volume-of-alerts and mean-time-to-resolution measure the work that the platform produces, not the work that catches an attacker. This paper looks at four metrics we routinely see harming fraud detection in the institutions we work with, and proposes four replacements.</description><pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate><category>paper</category><category>analysis</category><category>detection-engineering</category><category>fraud</category><category>metrics</category><category>SOC</category></item><item><title>[Paper] What to do if your business has just wired money to a fraudster</title><link>https://imfamericas.com/papers/2026-04-15-business-just-wired-money-to-a-fraudster/</link><guid isPermaLink="true">https://imfamericas.com/papers/2026-04-15-business-just-wired-money-to-a-fraudster/</guid><description>A short, prioritised checklist of the actions that materially affect whether the funds can be recovered. The first sixty minutes matter most; by the end of the working day the realistic recovery probability is meaningfully lower. Read this once before you need it.</description><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><category>paper</category><category>response</category><category>incident-response</category><category>business-payment-fraud</category><category>response-guide</category></item><item><title>[Paper] Joint advisory: shell-company exploitation in third-party payment processing</title><link>https://imfamericas.com/papers/2026-04-08-shell-company-tpp-exploitation-joint-advisory/</link><guid isPermaLink="true">https://imfamericas.com/papers/2026-04-08-shell-company-tpp-exploitation-joint-advisory/</guid><description>We are issuing this joint advisory together with five sector partners to draw attention to a sustained pattern of shell-company onboarding through third-party payment processors. The pattern moves between jurisdictions on a weekly cycle, exploits inconsistencies in beneficial-ownership data, and is currently observed against small-and-mid-sized payment processors in particular.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>paper</category><category>advisory</category><category>joint-advisory</category><category>financial-crime</category><category>third-party-payment-processing</category><category>shell-company</category></item><item><title>Detection engineering against low-and-slow operations</title><link>https://imfamericas.com/blog/2026-04-01-detection-engineering-against-low-and-slow/</link><guid isPermaLink="true">https://imfamericas.com/blog/2026-04-01-detection-engineering-against-low-and-slow/</guid><description>When the dwell time is measured in months rather than minutes, the detection problem stops being about signatures and becomes about baselines. Notes from a year of working financial-sector telemetry.</description><pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate><category>editorial</category><category>detection-engineering</category><category>baselines</category><category>financial-sector</category></item><item><title>On disclosure timelines: when ninety days is too long, when it is too short</title><link>https://imfamericas.com/blog/2026-03-15-on-disclosure-timelines/</link><guid isPermaLink="true">https://imfamericas.com/blog/2026-03-15-on-disclosure-timelines/</guid><description>The default coordinated-disclosure window of ninety days exists for reasons that are sometimes load-bearing and sometimes vestigial. A practitioner&apos;s view from inside financial-sector vulnerability work.</description><pubDate>Sun, 15 Mar 2026 00:00:00 GMT</pubDate><category>editorial</category><category>disclosure</category><category>coordinated-vulnerability-disclosure</category><category>editorial</category></item></channel></rss>