How Did Rippling Allegedly Catch a Deel Spy?

TL;DR

Rippling alleges that Deel cultivated an employee spy who repeatedly searched its systems for information about Deel and its customers. Rippling says it exposed the suspected activity with a fake Slack channel known only to selected executives, while Deel denies legal wrongdoing, calls the claims sensationalized, and says it intends to assert counterclaims.

Transcript

all right a sentence that has never been said before B2B Enterprise HR software space is the most riveting the most compelling espion story you'll ever hear I feel like this episode's going to have to start with the Netflix like d because this is a netlix original level drama so all right we got to do this story Parker Conrad who is the CEO of a co... Read More

Key Insights

• Rippling’s central allegation is that Deel cultivated an employee spy who conducted a long-running theft of trade secrets. The alleged activity included searching Rippling’s systems for Deel-related information and monitoring Deel customers who might have been considering a switch to Rippling.
• The suspected employee allegedly searched for Deel within Rippling’s systems an average of 23 times per day. Rippling interpreted that unusual frequency as potential evidence of systematic monitoring, although the hosts acknowledge that the publicly discussed account represents only one side of the dispute.
• Rippling’s honeypot was a fake Slack channel called “Deel Defectors,” supposedly containing conversations from former Deel employees. Rippling says almost nobody inside the company knew it existed, allowing any attempted access after Deel was notified to serve as a test of suspected information leakage.
• The attempted access allegedly occurred after Rippling informed selected Deel executives about the fake channel. Rippling reasoned that the narrow group of people who knew about it could help identify the source, although the transcript does not provide a final judicial finding validating that conclusion.
• The phone confrontation allegedly happened at Rippling’s Dublin office after local authorities became involved. According to the lawsuit’s account, the suspected employee said his phone was elsewhere, entered a bathroom, and failed to surrender it after being warned that deleting material could violate the law.
• The alleged bathroom response became a central dramatic detail because Rippling claims the employee said the risk was one he had to take. The transcript repeatedly presents this statement as an allegation from legal filings, not as an independently verified quotation or established fact.
• Deel’s response is that it denies all legal wrongdoing and plans to assert counterclaims. Its spokesperson characterized Rippling’s allegations as sensationalized and claimed the lawsuit was intended to shift attention from accusations involving sanctions law in Russia and alleged false statements about Deel.
• The hosts’ discussion is explicitly shaped by disclosed biases and incomplete information. One host invested in Deel, uses its product, and likes founder Alex, while both hosts repeatedly say the lawsuit contains allegations and that Deel has not yet presented its complete competing account.

Questions & Answers

Q: What did Rippling accuse Deel of doing?

Rippling accused Deel of cultivating a spy inside Rippling and orchestrating a long-running theft of trade secrets. According to the lawsuit described by the hosts, the suspected employee repeatedly searched internal systems for Deel-related information, including material concerning Deel customers who might have been considering switching to Rippling. Deel denies all legal wrongdoing and plans to assert counterclaims.

Q: How did Rippling allegedly identify the suspected spy?

Rippling allegedly noticed that an employee was searching for Deel unusually often within its systems, reportedly an average of 23 times per day. Its founder, legal team, and another executive then created a controlled test involving a fake Slack channel. An attempted login after selected Deel executives were told about the channel allegedly strengthened Rippling’s suspicions.

Q: What was the Deel Defectors Slack honeypot?

The “Deel Defectors” honeypot was a fake Slack channel created by Rippling and presented as a place where former Deel employees working at Rippling discussed Deel and disclosed sensitive information. Rippling says no ordinary employees participated in it. Selected Deel executives were informed that it existed, and someone allegedly attempted to access it the following day.

Q: Why was the fake Slack channel important to Rippling’s case?

The fake channel was important because knowledge of it was intentionally restricted. According to the hosts’ account, only a small group of Rippling executives and selected Deel executives knew it existed. When someone allegedly attempted to log in afterward, Rippling treated that access attempt as evidence connecting the confidential message sent to Deel with unauthorized access inside Rippling’s systems.

Q: What allegedly happened when the employee was asked for his phone?

According to Rippling’s account, the suspected employee was served and ordered to hand over his phone at the Dublin office. He initially said it was upstairs in his bag, but the bag reportedly contained only a laptop. He then entered a bathroom, allegedly used the phone inside, and left the premises without surrendering the device.

Q: Did the suspected employee flush his phone down the toilet?

The transcript does not establish that the phone was flushed. Rippling’s account says people outside the bathroom heard activity involving the phone and later heard a flush. Rippling reportedly ordered an inspection of the building’s plumbing, but no phone was found. The device’s fate therefore remained unresolved in the story as presented by the hosts.

Q: How did Deel respond to Rippling’s lawsuit?

Deel denied all legal wrongdoing and said it looked forward to asserting counterclaims. A spokesperson claimed Rippling was using sensationalized allegations to shift the narrative after being accused of violating sanctions law in Russia and spreading falsehoods about Deel. The transcript does not provide Deel’s complete evidentiary response or the details of its anticipated counterclaims.

Q: Are the allegations against Deel proven in the episode?

No, the episode does not present the allegations as proven. The hosts repeatedly describe the claims as allegations contained in Rippling’s lawsuit and acknowledge that every dispute has multiple sides. One host also discloses that he invested in Deel, likes its founder, and uses the product, making his potential bias clear while discussing the developing case.

Summary & Key Takeaways

• Rippling sued Deel, alleging that Deel cultivated a spy who conducted a long-running theft of trade secrets. According to Rippling’s account, the employee searched for Deel within Rippling’s systems an average of 23 times per day, potentially revealing information about Deel customers who were considering moving their business to Rippling.

• Rippling says its founder, legal team, and another executive created a honeypot to test their suspicions. They established a fake Slack channel called “Deel Defectors,” told selected Deel executives that it contained damaging conversations, and then observed an attempted login shortly afterward, allegedly connecting the confidential message to internal system access.

• The confrontation reportedly occurred in Rippling’s Dublin office, where the suspected employee was ordered to surrender his phone. Rippling alleges that he entered a bathroom, ignored warnings against deleting evidence, and left without providing the device. Deel denies wrongdoing and characterizes Rippling’s lawsuit as an attempt to redirect attention from separate accusations.

• The episode treats the dispute as both a serious legal controversy and an entertaining corporate espionage story. The hosts repeatedly stress that the allegations are unproven, disclose one host’s investment in Deel, acknowledge that only one side of the case was initially available, and anticipate Deel presenting counterclaims and its own account.