{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","favicon":"https://feed.craftedsignal.io/favicon-32x32.png","feed_url":"https://feed.craftedsignal.io/actors/alphv/feed.json","home_page_url":"https://feed.craftedsignal.io/","icon":"https://feed.craftedsignal.io/apple-touch-icon.png","items":[{"_cs_actors":["BlackCat","ALPHV","Noberus"],"_cs_cpes":[],"_cs_cves":[],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":[],"_cs_severities":["low"],"_cs_tags":[],"_cs_type":"threat","_cs_vendors":[],"content_html":"\u003cp\u003eThe \u0026quot;MaxMpxCt\u0026quot; registry value specifies the maximum outstanding network requests for the server per client, used when negotiating a Server Message Block (SMB) connection. Ransomware threat actors and operators (specifically BlackCat) have been observed increasing this value to handle a higher volume of traffic.\u003c/p\u003e\n\u003ch2 id=\"notes\"\u003eNotes\u003c/h2\u003e\n\u003cp\u003eIf the MaxMpxCt value is set beyond 125, older Windows 9x clients will fail to negotiate SMB connections.\u003c/p\u003e\n","date_modified":"2026-11-10T03:09:13Z","date_published":"2026-11-10T03:09:13Z","id":"https://feed.craftedsignal.io/briefs/2026-11-maxmpxct-registry/","summary":"BlackCat ransomware operators have been observed modifying the \"MaxMpxCt\" registry value to handle a higher volume of network traffic.","title":"Windows Server SMB MaxMpxCt registry configuration","url":"https://feed.craftedsignal.io/briefs/2026-11-maxmpxct-registry/"}],"language":"en","title":"CraftedSignal Threat Feed - ALPHV","version":"https://jsonfeed.org/version/1.1"}