Abstract

Ricin toxin is a plant‐derived, ribosome‐inactivating protein that is rapidly cleared from circulation by Kupffer cells (KCs) and liver sinusoidal endothelial cells (LSECs)—with fatal consequences. Rather than being inactivated, ricin evades normal degradative pathways and kills both KCs and LSECs with remarkable efficiency. Uptake of ricin by these 2 specialized cell types in the liver occurs by 2 parallel routes: a “lactose‐sensitive” pathway mediated by ricin's galactose/N‐acetylgalactosamine‐specific lectin subunit (RTB), and a “mannose‐sensitive” pathway mediated by the mannose receptor (MR; CD206) or other C‐type lectins capable of recognizing the mannose‐side chains displayed on ricin's A (RTA) and B subunits. In this report, we investigated the capacity of a collection of ricin‐specific mouse MAb and camelid single‐domain (VHH) antibodies to protect KCs and LSECs from ricin‐induced killing. In the case of KCs, individual MAbs against RTA or RTB afforded near complete protection against ricin in ex vivo and in vivo challenge studies. In contrast, individual MAbs or VHHs afforded little (<40%) or even no protection to LSECs against ricin‐induced death. Complete protection of LSECs was only achieved with MAb or VHH cocktails, with the most effective mixtures targeting RTA and RTB simultaneously. Although the exact mechanisms of protection of LSECs remain unknown, evidence indicates that the Ab cocktails exert their effects on the mannose‐sensitive uptake pathway without the need for Fcγ receptor involvement. In addition to advancing our understanding of how toxins and small immune complexes are processed by KCs and LSECs, our study has important implications for the development of Ab‐based therapies designed to prevent or treat ricin exposure should the toxin be weaponized.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.