The FBI is alerting art collectors and dealers to be particularly careful trading Near Eastern antiquities, warning that artifacts plundered by terrorist organizations such as ISIL are entering the marketplace.
“We now have credible reports that U.S. persons have been offered cultural property that appears to have been removed from Syria and Iraq recently,” said Bonnie Magness-Gardiner, manager of the FBI’s Art Theft Program.
The Bureau is asking U.S. art and antiquities market leaders to spread the word that preventing illegally obtained artifacts from reaching the market helps stem the transfer of funds to terrorists.
In a single-page document titled ISIL Antiquities Trafficking, the FBI asks leaders in the field to disseminate the following message:
- Please be cautious when purchasing items from this region. Keep in mind that antiquities from Iraq remain subject to Office of Foreign Assets Control sanctions under the Iraq Stabilization and Insurgency Sanctions Regulations (31 CFR part 576).
- Purchasing an object looted and/or sold by the Islamic State may provide financial support to a terrorist organization and could be prosecuted under 18 USC 233A.
- Robust due diligence is necessary when purchasing any Syrian or Iraqi antiquities or other cultural property in the U.S. or when purchasing elsewhere using U.S. funds.
In February, the United Nations Security Council unanimously passed Resolution 2199, which obligates member states to take steps to prevent terrorist groups in Iraq and Syria from receiving donations and from benefiting from trade in oil, antiquities, and hostages.
As part of a broad U.S. government response, the Department of State this spring published satellite imagery showing industrial-level looting at Syrian and Iraqi archaeological sites. In a May raid against the now deceased ISIL finance chief Abu Sayyaf in Syria, U.S. Special Operations Forces recovered a significant cache of archaeological and historical objects and fragments.
Deprecated: related_posts is deprecated since version 5.12.0! Use yarpp_related instead. in /srv/users/ibn/apps/ibn/public/wp-includes/functions.php on line 5211