The plot thickens. Did the meant Twister Money developer arrested in The Netherlands have ties to a Russian safety company? Is a task in 2017 for an organization with tenuous connections to Russia sufficient to justify the arrest? As Bitcoinist told you and reiterated, there needed to be one more reason that FIOD and the OFAC arrested a easy Twister Money coder. Is that this one it? We don’t have reputable affirmation but, however it could be.
It sounds as if, the alleged Twister Money developer used to be Aleksey Pertsev, CEO of PepperSec and resident of The Netherlands. The details about his meant ties to Russian intelligence comes courtesy of Kharon. The corporate “supplies knowledge and analytic gear to optimize the core purposes of monetary crimes compliance methods, together with KYC, screening, and investigations.”
How Are PepperSec And Twister Money Comparable?
Their record states that Twister Money “runs on instrument code advanced via PepperSec, Inc.” What and the place is that corporate precisely?
“PepperSec is a Delaware-registered company with its number one office in Seattle, Washington, in step with a 2020 SEC submitting. PepperSec’s site describes the corporate as a safety consulting company of white hat hackers.”
Recently, the website in question contains an “About Us” that claims:
“We’re skilled safety engineers seasoned via a few years of sensible revel in and deep figuring out of applied sciences. We’re able to fight to make your venture as safe as imaginable.”
Truthful sufficient, however…
How Is PepperSec Attached To Russia?
It sounds as if, Kharon reviewed “private and corporate profiles” and decided that Aleksey is PepperSec’s CEO. To this point, so just right. The place’s the smoking gun, even though? Again to Kharon’s record:
“In 2017, Pertsev used to be a data safety specialist and developer of sensible contracts for Virtual Safety OOO, in step with an archived model of the corporate’s site reviewed via Kharon. Virtual Safety OOO is a Russian entity designated via the U.S. Treasury Division in 2018 for offering subject matter and technological beef up to the FSB, Russia’s number one safety company. Treasury alleged that, as of 2015, Virtual Safety labored on a venture that might build up the offensive cyber features of Russia’s intelligence services and products.”
That’s tenuous, to mention the least. And under no circumstances associated with Twister Money. Alternatively, a caveat is that the opposite two “PepperSec’s founders — U.S.-based Roman Hurricane and Russia-based Roman Semenov” haven’t been touched. To this point. So, the case could be towards Aleksey Pertsev on my own.
ETH worth chart for 08/26/2022 on FTX | Supply: ETH/USD on TradingView.com
How Does All Of This Relate To Twister Money?
For this phase, we’ll flip to quotes from notorious bitcoin enemy “Fortune.” The magazine interviewed Nick Grothaus, vice chairman of analysis at Kharon, who mentioned:
“You had this man running for [Digital Security OOO] and doing pen checking out himself, after which Treasury designated the corporate for serving to the FSB’s hacking features.”
Good enough, we didn’t know concerning the “pen checking out” phase. Alternatively, how does this relate to Twister Money? To respond to that query the mag lodges to Alex Zerden, “an accessory senior fellow on the Middle for a New American Safety,” who mentioned:
“This opens up numerous credibility problems for the builders of Twister Money. That is lovely profound data that informs why the U.S. govt and Dutch government have taken sure movements.”
Does it, even though? “There appears to be a extra complicated and sophisticated image that takes extra time to get to the bottom of,” Zerden added. And we agree. That’s why the EFF asked for clarity across the Twister Money scenario. As Bitcoinist already said, “perhaps the OFAC has a greater case and the developer is responsible of one thing else. If that’s the case, with “clarifying data and lowering the anomaly” the OFAC would have have shyed away from this entire scenario.”
Featured Symbol: Graphic twister from this blog post | Charts via TradingView