“How Mossad Poisoned the Entire Hamas Military Council at a Commander’s Son’s Wedding”

"How Mossad Poisoned the Entire Hamas Military Council at a Commander's Son's Wedding"

News Media Nigeria

“How Mossad Poisoned the Entire Hamas Military Council at a Commander’s Son’s Wedding”

 

Advertisement
Ad imageAd image

Gaza Strip, August 1999. By the late 1990s, Hamas’s military command had become one of the most difficult targets in the Middle East. Its senior commanders operated without fixed schedules, without predictable locations, and without any exposure that Israeli intelligence had been able to exploit.

Advertisement
nlngnlng

Each of them had outlasted multiple attempts to reach them. Together they had spent years directing the organization’s armed operations across the Gaza Strip. And together they had never once appeared in the same place at the same time until the third week of August when one of them decided to give his son a wedding. Msad received the intelligence 31 days before the ceremony.

What they did with it would come to involve a woman, a family pastry shop in Conunus, and a method that left no trace in any hospital, any laboratory, or any investigation that followed. Could one woman reach the most protected table in Gaza and walk away alive?

Advertisement
Ad imageAd image

To understand what made this particular wedding so significant, not for the family, but for the men who attended it, it is necessary to understand the security architecture Hamas had built around its military command in the years following Oslo. The Oslo Accords of 1993 had fundamentally altered the operating environment for every armed faction in the Palestinian territories.

The Palestinian Authority, now formerly established in Gaza and the West Bank, carried both the political incentive and the international obligation to constrain Hamas’s military activities. Israeli intelligence, meanwhile, had significantly intensified its targeting operations against Hamas’s operational leadership.

A period that included the assassination of Yaya Aayash in January 1996, the bombing expert, the organization called the engineer, and one of the most operationally valuable figures the military wing had ever produced. The combined effect of Palestinian Authority pressure from within and Israeli targeting from without had forced Hamas’s military wing to implement a structural response that by 1999 had become the defining feature of how its senior leadership operated.

Deliberate systematic separation. The military council, the body responsible for authorizing and directing Hamas’s armed operations across the Gaza Strip, functioned through a structure of layered intermediaries that ensured its members never needed to be in the same physical space to make collective decisions.

Advertisement
Ad imageAd image

Orders moved downward through cutouts. Intelligence moved upward through separate channels. Senior commanders changed residences on irregular schedules, avoided social gatherings where their presence could be anticipated, and maintained personal security routines that Israeli analysts had described as among the most disciplined in any non-state armed organization in the region.

It had worked for years. It had worked. What no security doctrine had ever been designed to handle was the social obligations of a community that had known these men since before they were commanders. In Palestinian society and in Gaza’s communities specifically, the rituals of collective life carry a weight that exists entirely outside the frameworks of operational security.

A wedding is not merely a private family event. It is a public declaration of social standing, a collective affirmation of community bonds, and an occasion governed by norms of obligation that reach across every level of the social structure. To decline an invitation to the wedding of a colleagueu’s son, a man you have known for decades, whose struggles you have shared, whose family has shared meals with yours, is not a calculated security decision.

In the cultural register of Gaza in 1999, it is an act of social rupture. The kind of absence that is noticed, discussed, and not forgotten. Every man who received that invitation had grown up inside the same web of obligation that it came from. All of them came. The man at the center of the event was Ibrahim Al-Mazri, the chairman of Hamas’s military council and the father of the groom.

Al-Mazri was 53 years old and had been part of the organization since its founding period in the late 1980s. He was not a figure who appeared in any public context. No interviews, no statements, no photographs in any archive that Israeli intelligence had built from open sources.

Over the four years preceding August 1999, MSAD’s targeting division had been unable to establish even the approximate location of his primary residence with any confidence.

 

 

The wedding was the one event his security doctrine could not eliminate because the wedding was his. Kamal Nazal arrived as the council’s director of operations, the man responsible for translating strategic decisions into operational orders and maintaining command relationships with the field commanders who executed them.

 

Nazal was 47 years old. He had survived a direct Israeli targeting attempt in 1996 and had rebuilt his security arrangements around the assumption that MSAD would try again. He was assessed as the most operationally capable figure on the council, methodical, experienced, and almost impossible to anticipate. Eliminating him had been a standing priority for MSAD’s targeting division since 1995.

 

 

Ysef Alberawi had spent three years in Sudan in the early part of the decade, developed working relationships with Iranian procurement networks during that period and returned to Gaza in 1994 to build a logistics infrastructure that Israeli analysts had spent years attempting to map without success.

 

He was 42 years old and his value to the organization lay not in the operations he directed but in the supply architecture he maintained one that Israeli planners considered among the most difficult targets in the territory to disrupt. Fati Hamdan was 49 years old and held the council’s intelligence coordination portfolio, responsible for Hamas’s internal counter inelligence function and for managing sources inside the Palestinian authorities security services.

 

Considered by Israeli analysts to be the most intellectually rigorous figure on the council, his work was defensive in nature, but his knowledge of the organization’s internal security architecture made him, from MSAD’s perspective, one of the most sensitive names on any targeting list. Rasheed Al-Katib, 44 years old, managed the financial architecture that made everything else possible, overseeing the movement of funds from Iranian state channels, Gulf private donors, and diaspora fundraising networks that collectively sustained Hamas’s

 

operational budget. Israeli intelligence assessments consistently pointed toward operational budgets significantly larger than any external analysis had suggested and consistently pointed toward Alcatib as the man who controlled them. Mawan Abua was the youngest full council member at 39 serving as field operations commander for the northern Gaza Strip.

 

The figure who maintained direct working relationships with the cell networks responsible for attack planning along the northern perimeter. He had risen through the ranks faster than any comparable figure in the organization’s history and was assessed as aggressive, effective under pressure and willing to authorize operations that more senior members sometimes deferred.

 

The seventh member was Salai Al- Yazuri. He was 56 years old, the oldest and longest serving figure on the council, its institutional memory, and the man who had known every significant Hamas commander since the organization’s earliest days. He had outlasted three distinct phases of Israeli targeting campaigns through extreme personal caution and an almost total absence of predictable routine.

Israeli analysts described him as the council’s stabilizing figure. The man whose judgment was sought when decisions were genuinely difficult and whose presence in any room changed how the other members conducted themselves. He was also, as Israeli intelligence had documented through medical intercepts collected over the preceding 2 years, a diabetic.

He managed the condition through a carefully restricted diet and was known within Hamas’s internal social circles to decline sugar-based foods at every occasion he attended, not as a preference, as a medical necessity. This detail appeared in a background intelligence file. At the time it was recorded, it was considered a minor personal fact, the kind of information that fills the margins of a comprehensive profile without suggesting any operational relevance.

It would become the most consequential detail in the entire operation. MSAD received the intelligence about the wedding 31 days before the ceremony. The source was not embedded inside Hamas’s military structure. It was a contact several degrees removed from the core. The kind of person who absorbed information not because they were trusted with it, but because they moved through environments where it was spoken aloud.

A date, a location, a name. By the time it had traveled through two intermediate contacts and reached a MSAD handler outside Gaza, signals intelligence had confirmed its accuracy. The wedding was real. The date was fixed. The planning session in Tel Aviv opened within 48 hours. The question was not whether the opportunity warranted a response.

The question was whether any method of action was feasible within 31 days inside a closed private event in a city where MSAD had no established operational infrastructure targeting men whose security arrangements had deflected every previous approach. The answer came not from the operational roster or the weapons inventory.

It came from an analyst reviewing a background file on the Almazri family’s social history. a file compiled four years earlier that had sat in the archive without generating any operational interest since the day it was written. What that file contained and why a single detail about a pastry shop in Conunus would change everything is where this story truly begins.

The file had been compiled in 1995 by an analyst in MSAD’s Gaza Desk whose primary assignment was building biographical profiles of senior Hamas figures and their immediate family networks. The work was largely preparatory. Intelligence gathered not because a specific operation was imminent, but because comprehensive background files on priority targets were considered standing assets, available to be drawn on whenever operational planning required them.

 

 

Most of the file on Ibrahim al- Mazeri covered predictable ground, family history, known associates, documented movements, assessed security arrangements. Four pages into the background section under a subheading covering the Al-Mazri family’s social and ceremonial patterns was a single paragraph about food.

The family, the file noted, had used the same pastry supplier for all major social occasions for approximately a decade. The supplier was a small confectionary workshop in Conunus operated by a man named Khalil Barakat, a craftsman in his late 50s who had been producing traditional sweets for Gaza’s communities since the early 1980s.

The Al-Mazri family’s relationship with Barakat predated Ibrahim Al- Mazri’s rise to any position of significance within Hamas. It was, in the analyst’s assessment, a straightforwardly social and cultural relationship. the kind of long-standing commercial loyalty that characterizes family life across Gaza’s communities, where trusted craftsmen are retained across generations and where switching suppliers for a significant occasion would be considered at minimum unusual.

The analysts who had written those four sentences had intended them as contextual background. They were not flagged as operationally relevant. They had generated no follow-up inquiry in the four years since the file was completed. When the planning team pulled the file on the morning after the wedding intelligence was verified, the analyst reading it reached those four sentences, read them twice, set the document down, and went to find the head of the planning session.

The conversation that followed lasted less than 20 minutes. By the end of it, the operational logic of the entire approach had shifted. Bericott’s workshop was not merely a supplier. It was the single point in the Almazeri family ceremonial life where an external presence could plausibly exist, where the products that would reach the wedding table originated, where access, if it could be established, would require no physical penetration of the event itself, and where a credible professional reason to be present,

needed no explanation to anyone. The planning team had spent 48 hours looking for a way into a closed highsecurity private event. The answer had been sitting in a 4-year-old archive file, waiting for someone to ask the right question. The question was now whether access to that workshop already existed.

 

It did. And the reason it existed had nothing to do with the wedding. It had to do with a decision made eight months earlier by a different desk for a different operational purpose that had placed a specific person in a specific location that no one at the time of placement had imagined would ever matter like this.

 

Her operational file used a cover name inside the planning team in the days that followed. She was referred to simply as the baker. Her actual background was the kind that MSAD’s recruitment division encountered rarely enough that it was considered a significant asset. She had been born in Gaza, raised in Israel, and trained as a pastry chef.

 

Each of those facts, taken individually, was unremarkable. Together, they produced a profile that was for a very specific category of operational requirement almost impossible to replicate. She had been born in 1971 in Gaza City, the second daughter of a Palestinian family that had left the territory in 1973 in the years of economic migration that followed the 1967 war.

 

Her father had found work in Israel’s construction sector. The family settled near Tel Aviv and remained. She grew up speaking Arabic at home, Gaza Arabic, the dialect of the communities she had been born into, and Hebrew at school. She moved between both languages and both social registers with the ease of someone who had never been required to choose between them.

 

Gaza was present in her household as a memory, a set of food traditions, a particular register of spoken Arabic, and the accumulated texture of a community identity that does not require geography to survive. She studied at a culinary school in Tel Aviv in the early 1990s and subsequently trained under a pastry specialist for 2 years, developing a technical foundation in traditional Middle Eastern confectionary that was by the assessment of those who later evaluated it genuinely professional. Her knowledge of mamu, of

 

date-based and nut-based preparations, of the regional variations in technique that distinguished one community’s traditional sweets from anothers, was not a fabricated cover attribute. It was real. It had been acquired before anyone from any intelligence service had ever spoken to her. The initial approach came in 1997 through a contact in Tel Aviv’s professional culinary community who had no knowledge of the operational purpose behind the introduction.

 

The meeting was framed as a professional conversation. It lasted 2 hours. The officer who conducted it submitted an assessment the following day describing her as operationally suitable on every relevant dimension. Linguistic fluency without detectable Israeli markers. technical expertise capable of withstanding professional scrutiny, psychological stability under simulated pressure, and a personal history that would support a cover identity inside Gaza without requiring fabricated biographical elements that could fail.

 

under close examination. The recruitment process took 4 months. What she was told about the nature of future assignments was limited to what was necessary. She would be deployed in environments requiring her professional skills, operating under a cover identity. The specific content of any assignment would be disclosed on a need to- know basis as operational planning developed.

She accepted these terms without pressing for more. A preparation lasted 11 months and covered the standard framework for agents operating under non-official cover, surveillance, detection, cover maintenance under sustained questioning, communication security, and emergency protocols. A supplementary module addressed the specific requirements of operating within Gaza’s communities, the social registers, the behavioral norms, the ways in which an outsider could be identified, not through documents or language, but through the

subtler markers of someone who did not know intuitively how people in that environment moved and conducted themselves. She had fewer gaps to fill in that module than any comparable trainee her instructors had worked with. Gaza Arabic was not a learned skill. It was the first language she had ever heard spoken.

 

In November of 1998, she was deployed to KHNUNIS under a cover identity as a Palestinian woman from the diaspora, reconnecting with her background and pursuing her professional work. The cover was internally consistent and supported by documentation prepared to withstand the level of scrutiny she was likely to encounter.

 

Within 6 weeks of her arrival, she had secured a position as an apprentice at Khalil Barakat’s confectionary workshop. Not through any operational maneuver, but through the most direct means available. She walked in, introduced herself, explained her background, and asked if there was work. Bericat, managing a small operation with periodic seasonal demand that exceeded what his regular staff could handle, hired her after a single conversation.

 

For the 8 months that followed, she worked not as someone performing a staged role, but as a working pastry apprentice, doing what pastry apprentices do, preparing dough, managing fillings, operating the ovens, handling orders. Barrier was a craftsman who had been refining his methods for decades, and he taught with the particular thoroughess of someone who took the transmission of craft knowledge seriously.

 

She learned his recipes. She learned his production rhythms. She learned which families ordered what and when and why. She learned, among many other things, that the Al-Mazeri family ordered from this workshop for every significant occasion they hosted and had done so without exception for as long as anyone in the workshop could remember.

 

She had reported this through the standard communication channel months before the wedding was ever announced. It had been logged, filed, and had generated no operational interest until an analyst in Tel Aviv read four sentences in an old archive file and went to find the head of the planning session.

 

What she knew at the point when that connection was made was only what she had always known. Her assignment was open-ended, and the handler she communicated with would tell her what she needed to know when she needed to know it. She did not know that a wedding had been announced. She did not know that a guest list had been verified.

 

She did not know that the workshop she had spent 8 months inside had just become the operational center of the most significant targeting operation MSAD had attempted in Gaza in years. She was at work in Barakat’s kitchen on a morning in late July when her handler made contact through the established channel. The message was brief.

 

It told her to remain in place, maintain her cover without any change in behavior, and wait for further instruction. She waited. Did she know on the day Barracat asked her to help with the wedding order that those 8 months had been building toward this single moment? Or was it for her just another working day? The compound had no commercial name and no entry in any published chemical database.

 

inside the division that had developed it. It was referred to by a four-digit internal designation that appeared in no literature accessible to anyone outside a classified research program that had been running without broad institutional knowledge for nearly 4 years. To the planning team that received the technical briefing in the first week of August 1999, it became known simply as the material.

 

It was not the first time MSAD’s chemistry division had deployed a compound of this category in the field. A similar mechanism had been used in an operation in Beirut 3 years earlier under circumstances that the planning team was briefed on in outline but not in detail. The Beirut operation had worked.

 

 

The question was whether the same approach would hold in a different environment with a different delivery method and a target group significantly larger than anything previously attempted. What the material was precisely was a synthetic compound engineered to interfere with a specific mechanism in human cellular metabolism. Not immediately and not visibly but gradually accumulating in tissue over time until the threshold for systemic failure was crossed.

 

The physiological process it initiated was not dramatic. It did not produce convulsions, visible hemorrhage, or any of the acute presentations that would alert a clinical observer to poisoning. What it produced over a period of 44 to 52 hours following administration was progressive multiorgan dysfunction, a cascading failure of the body’s regulatory systems that presented to any physician encountering it without fornowledge as the kind of severe metabolic crisis that can occur in patients with no

 

prior history of serious illness. The terminal presentation was indistinguishable on standard clinical assessment from acute organ failure of internal origin. No external agent, no foreign substance, no evidence of anything other than a body that had catastrophically and without apparent cause stopped functioning.

 

The compound was theable. This was not a secondary property. It was the central engineering requirement that had driven three years of development work. Any substance intended for introduction into food had to survive the temperatures of baking without degrading into either an inert byproduct or a detectable residue.

 

The material met this requirement fully. It remained active at the temperatures used in traditional pastry preparation, bonded without reaction to both oil-based and water-based preparations and produced no alteration in the color, texture, aroma, or flavor of any food into which it was introduced.

 

A person eating it would notice nothing. A person standing beside someone who was preparing it would notice nothing. Standard toxicological screening panels available in Gaza’s medical facilities in 1999 would not identify it. Even a targeted forensic analysis, the technical officer explained during the planning briefing, would find nothing after 60 hours because the compound’s metabolic byproducts were chemically indistinguishable from normal cellular waste.

 

The evidence, by the time the clinical picture became clear, would already have destroyed itself. The planning team received this briefing over two sessions held on consecutive days in the first week of August. The technical officer who delivered it was precise and systematic, and he answered every question the team raised with the careful specificity of someone who had spent years preparing for exactly this kind of conversation.

 

 

There was one question, however, that his answer could not fully satisfy. Had the compound ever been administered to a human subject? The answer was no, not directly. The compound had been validated through biological modeling that the chemistry division considered conclusive. The team was being asked to accept that assessment entirely on faith.

 

Two members of the planning team noted their reservations formally. They were recorded and set aside. The operational window was 31 days from the original intelligence receipt and by the time the technical briefing concluded 18 of those days had already passed. There was no time for additional validation and no alternative mechanism available.

 

The decision to proceed was made at a level above the planning team and communicated without ambiguity. The material would be used. The question of how it would be introduced was the only remaining question. The answer had already been determined by the structure of the operation itself. The wedding suites were the delivery vehicle.

 

Specifically, the traditional Mamu, the date-filled shortbread that is the centerpiece of every significant celebration in Gaza’s communities and that the Al-Mazri family had ordered from Barakat’s workshop for every occasion they had hosted in the past decade. Mammul was the correct vehicle for three reasons.

 

The planning team identified within the first hour of working through the options. First, it was a preparation in which a filling was enclosed inside a dough casing, meaning the compound could be introduced into the filling itself, completely sealed from any external contact or inspection. Second, it was served toward the end of a social gathering after hours of food and drink had already been consumed, reducing any possibility that an unusual reaction would be connected to a specific dish.

 

Third, and most critically, it was traditional. A wedding in Gaza without Mamu on the table would be an occasion the guests would remember as unusual. With it present, no one would give it a second thought. The operational plan called for two entirely separate batches. The first was a standard production run prepared for the general wedding guests.

 

Traditional mamu made to Barericat’s normal recipe without any modification. The second was a 700 g batch prepared separately with the compound introduced into the date filling at a concentration calculated to deliver a lethal dose to a person of average body weight consuming a normal serving of two to three pieces. This second batch was designated exclusively for the commander’s table, a separate arrangement at the wedding where the most senior guests would be seated apart from the general gathering, as was customary at significant events

 

in Gaza’s social hierarchy. The physical separation of the two tables meant that the modified batch would reach only those it was intended for. The rest of the guests would eat from the standard run. No one else was at risk. The dosing calculation had been prepared by the technical officer and reviewed three times before being passed to the handler who would communicate it to the operative.

 

The concentration had been calibrated with precision, high enough to guarantee lethality in any person who consumed a standard serving, low enough to produce no detectable alteration in the filling’s appearance or texture. The date paste used in traditional mamole, dark, dense, and richly flavored, was the technical officer noted, the ideal medium for this kind of introduction.

 

Its natural properties masked any chemical presence completely and unconditionally. The operative received the compound through a dead drop in communis on the 4th of August. The transfer consisted of a single sealed container, small enough to be carried in a coat pocket, passed through a contact she had never met before, and would never meet again.

Along with it came a written instruction in Arabic, formatted to resemble the kind of note a professional chef might write to herself, specifying the quantity to be used, the precise stage of preparation at which it should be introduced, and the requirement that it be mixed into the filling thoroughly and evenly before the dough casing was applied.

The note was to be destroyed after reading. She destroyed it the same evening. The wedding was scheduled for the 18th of August. The convectionary order had been placed with Bericat’s workshop 10 days earlier, a large commission covering multiple types of traditional suites for several hundred guests. When the full scale of the order became clear, Bericat asked her to work additional hours to help manage the production volume.

She agreed without hesitation. There was nothing unusual in the request. It was exactly the kind of seasonal surge that a small workshop with a well- reggarded community reputation regularly encountered during wedding season. She had helped with similar large orders twice before during her 8 months at the workshop.

Bareric trusted her work without qualification. He had no reason not to. On the morning of the 17th of August, the day before the wedding, she prepared both batches. The general batch came first, produced through the standard process she had absorbed across 8 months of daily work in the workshop.

The semolina dough, the date filling prepared according to Barericat’s established recipe, the careful shaping in the traditional carved wooden molds, the oven. Barricat was present for part of the morning, moving between the front of the shop and the preparation area, managing other elements of the large order. He did not watch her continuously.

There was no reason to. She was, by every measure available to him, a competent and reliable apprentice who had given him not a single cause for concern across 8 months of daily contact. The second batch followed. The process was identical in every respect visible to any observer. The same dough, the same technique, the same molds.

The single difference took less than 30 seconds to execute and produced no visible audible or olfactory change in any property of the finished product. The two batches were packaged separately, labeled according to their destination table and set aside with the rest of the order for delivery the following morning.

The confectionary was loaded onto a vehicle and transported to the wedding venue. She was not part of the delivery. Her role in the preparation had ended when she placed the packages on the shelf. The commanders would be seated at their table the following day. The Mamu would be placed in front of them. And in the planning rooms in Tel Aviv, the people who had built this operation over 31 days were waiting for news that would not arrive for another 48 hours.

 

Were all of the commanders going to eat from that plate? or would one of them, for any reason, pass? The 18th of August began early at the Al-Mazri family compound in the southern outskirts of Gaza City. By midm morning, vehicles were arriving in steady succession. relatives, neighbors, members of the community who had known the family for decades, and at intervals that suggested careful individual timing, the senior figures, whose presence transformed a family celebration into something that carried

a different kind of weight. Each of the council members arrived separately. Each was accompanied by at least one personal security attendant. Each was greeted at the entrance by members of the Al-Mazari family’s own security arrangement, men who checked faces against expected guests and waved through those they recognized.

The precautions were visible but not oppressive. This was, after all, a wedding. The venue was a large private property with an interior courtyard and several connected reception spaces. The general guests occupied the main courtyard where tables had been arranged in the traditional pattern and where the food, music, and the accumulated warmth of a large community gathering created the particular atmosphere of a Gaza wedding in summer.

Dense, loud, celebratory, and entirely genuine. Separate from this, at the far end of the main reception hall, a distinct table had been arranged for the senior guests. It was set apart from the main gathering by both physical distance and the quiet presence of security personnel positioned at the approaches.

 

 

Part 1……..

 

 

Share This Article
Leave a Comment