|Crack monero, blackjack and whores|
Well, the shizo is in touch again. Today we will talk about the expensive shit CipherTrace and not only.
First of all, though belatedly, I want to congratulate everyone involved on the 8th anniversary of the first release of Monero (April 18, 2014). Next, I recommend reading on reddit about the categories of monero haters. Monero, as some people think, is a token, although in fact it is a coin with its own blockchain network.
It has been almost 6 years since the first acquaintance with this cryptocurrency and what I would like to say, during this time I have heard so many times about tracking monero and "magic" tools for this, however, during the period I have consulted various persons (at times I came across those who are engaged in fierce blackness) and used the basic rules of concealment of identity in financial manipulations in the network, and no one was caught. But, this does not mean that they have become elusive.
Undoubtedly, bitcoin is not about anonymity (all sorts of mixers do not really save), so for serious purposes, even if you still have the desire to use it, you will have to try hard. There are undoubtedly many guides on the web about ways to "not be able" to track bitcoin transactions (example ) . But the funny thing is that most of the articles talk about using tor, mixers, VPN "not storing" logs (it's very funny, even raising your own is safe, but it won't solve the problem much) and buying/selling bitcoin for cache (this will make it even more fun). Okay, the topic is not about bitcoin, it's better to analyze its "anonymyzation" separately.
So, back to the question about Monero.
I think many people have heard about the spam attack on monero, when everything was just beginning or about the unfinished from sybil . Or about "Monero badcaca ", if the spam attack could still really be called successful (any tx in the block were changeable for the attacker in positions 512 and 513, provided they are identical in dimension and validity), then the previous ones are some kind of babble.
Further - more interesting. The US Internal Revenue Service (IRS) signed contracts with Chainalysis and Integra FEC for a total of $ 1.25 million, how did it end? A tool from ChipherTrace has appeared to track transactions, which did not justify itself, and moreover, they ask for 16 thousand dollars for such shit, although it can only track the chain with a certain probability, that is, there are no guarantees. And the amount of 1.25 million is ridiculous for such a thing. You can read more here .
At the Blockchain Alliance webinar in December 2019, Jerek Jakubcek (from Europol) said that the suspect who used the monero + Tor bundle was not tracked (the IP address was not tracked), there are attacks/audits on Tor and Monero on the work channel, you can look at the tags #tor and #xmr.
Here is the actual article about the inefficiency of the monero tool from ChipherTrace and an interview CEO of CipherTrace with a developer confirming the low efficiency of this shit.
The easiest way, when asked, is to run monero this way:
./monerod --tx-proxy tor, 127.0.0.1:9050
So far, using Zcash and Monero is probably a good move to maintain anonymity. Now I am communicating with the developers of one tullza to compare a user using xmr as an electronic currency (a coin with a blockchain) and I want to say that it is currently impossible to guarantee the owner of the wallet at the address, and a one-time wallet is generally impossible from the point of view of mathematics and cryptography.
Summing up, I would like to say that if you see an article / work / book about the monero crack, and there is no clear algorithm and confirmation of the result, then how it applies to everything is empty talk.
#shizo #xmr #deanonymization
Well, the shizo is in touch again. Today we will talk about the expensive shit CipherTrace and not only.
First of all, though belatedly, I want to congratulate everyone involved on the 8th anniversary of the first release of Monero (April 18, 2014). Next, I recommend reading on reddit about the categories of monero haters. Monero, as some people think, is a token, although in fact it is a coin with its own blockchain network.
It has been almost 6 years since the first acquaintance with this cryptocurrency and what I would like to say, during this time I have heard so many times about tracking monero and "magic" tools for this, however, during the period I have consulted various persons (at times I came across those who are engaged in fierce blackness) and used the basic rules of concealment of identity in financial manipulations in the network, and no one was caught. But, this does not mean that they have become elusive.
Undoubtedly, bitcoin is not about anonymity (all sorts of mixers do not really save), so for serious purposes, even if you still have the desire to use it, you will have to try hard. There are undoubtedly many guides on the web about ways to "not be able" to track bitcoin transactions (example ) . But the funny thing is that most of the articles talk about using tor, mixers, VPN "not storing" logs (it's very funny, even raising your own is safe, but it won't solve the problem much) and buying/selling bitcoin for cache (this will make it even more fun). Okay, the topic is not about bitcoin, it's better to analyze its "anonymyzation" separately.
So, back to the question about Monero.
I think many people have heard about the spam attack on monero, when everything was just beginning or about the unfinished from sybil . Or about "Monero badcaca ", if the spam attack could still really be called successful (any tx in the block were changeable for the attacker in positions 512 and 513, provided they are identical in dimension and validity), then the previous ones are some kind of babble.
Further - more interesting. The US Internal Revenue Service (IRS) signed contracts with Chainalysis and Integra FEC for a total of $ 1.25 million, how did it end? A tool from ChipherTrace has appeared to track transactions, which did not justify itself, and moreover, they ask for 16 thousand dollars for such shit, although it can only track the chain with a certain probability, that is, there are no guarantees. And the amount of 1.25 million is ridiculous for such a thing. You can read more here .
At the Blockchain Alliance webinar in December 2019, Jerek Jakubcek (from Europol) said that the suspect who used the monero + Tor bundle was not tracked (the IP address was not tracked), there are attacks/audits on Tor and Monero on the work channel, you can look at the tags #tor and #xmr.
Here is the actual article about the inefficiency of the monero tool from ChipherTrace and an interview CEO of CipherTrace with a developer confirming the low efficiency of this shit.
The easiest way, when asked, is to run monero this way:
So far, using Zcash and Monero is probably a good move to maintain anonymity. Now I am communicating with the developers of one tullza to compare a user using xmr as an electronic currency (a coin with a blockchain) and I want to say that it is currently impossible to guarantee the owner of the wallet at the address, and a one-time wallet is generally impossible from the point of view of mathematics and cryptography.
Summing up, I would like to say that if you see an article / work / book about the monero crack, and there is no clear algorithm and confirmation of the result, then how it applies to everything is empty talk.
#shizo #xmr #deanonymization
👍7👏5
|OrNetRadar|
Репозиторий с группами ретрансляторов(relays) в сети Tor, которые обнаруживаются в автоматическом режиме.
Почитать про мотивацию для создания репозитория можно почитать тут. Если вкратце - наплыв вредоносных ретрансляторов в торе. Автор ещё с 2017 года находится в закрытом списке рассылки Tor Project для подтверждения вредоносности ретрансляторов в тор. Далее, с 2019 года он начал отправлять репорты в public tor-talk. Про Sybil атаку, связанную с монеро прикреплял ссылку выше, можно тут и ещё тут посмотреть.
Также прикладываю ниже работу про идентификацию и характеристику Sybil в сети Tor.
Вот ещё несколько ссылок про зараженные relays и не только:
🦠Tor Network: Malicious Exit Relay and DNS Resolution
🦠Malicious Tor Network Servers Are Targeting Users’ Cryptocurrencies
🦠How malicious Tor relays are exploiting users in 2020
💥Типы ретрансляторов(torproject)
💥Relay Search
A repository with groups of repeaters(relays) in the Tor network that are detected automatically.
You can read about the motivation for creating a repository here . In short, there is an influx of malicious repeaters in the Tor. The author has been on the TorProject closed mailing list since 2017 to confirm the harmfulness of repeaters in the tor. Further, from 2019 he started sending reports to public tor-talk . About the Sybil attack related to monero attached the link above , you can here and here to see.
I also attach the work below about the identification and characterization of Sybil in the Tor network.
Here are some more links about infected relays and not only:
🦠Tor Network: Malicious Exit Relay and DNS Resolution
🦠Malicious Tor Network Servers Are Targeting Users’ Cryptocurrencies
🦠How malicious Tor relays are exploiting users in 2020
💥Types of relays(torproject)
💥Relay Search
#shizo #tor
Репозиторий с группами ретрансляторов(relays) в сети Tor, которые обнаруживаются в автоматическом режиме.
Почитать про мотивацию для создания репозитория можно почитать тут. Если вкратце - наплыв вредоносных ретрансляторов в торе. Автор ещё с 2017 года находится в закрытом списке рассылки Tor Project для подтверждения вредоносности ретрансляторов в тор. Далее, с 2019 года он начал отправлять репорты в public tor-talk. Про Sybil атаку, связанную с монеро прикреплял ссылку выше, можно тут и ещё тут посмотреть.
Также прикладываю ниже работу про идентификацию и характеристику Sybil в сети Tor.
Вот ещё несколько ссылок про зараженные relays и не только:
🦠Tor Network: Malicious Exit Relay and DNS Resolution
🦠Malicious Tor Network Servers Are Targeting Users’ Cryptocurrencies
🦠How malicious Tor relays are exploiting users in 2020
💥Типы ретрансляторов(torproject)
💥Relay Search
A repository with groups of repeaters(relays) in the Tor network that are detected automatically.
You can read about the motivation for creating a repository here . In short, there is an influx of malicious repeaters in the Tor. The author has been on the TorProject closed mailing list since 2017 to confirm the harmfulness of repeaters in the tor. Further, from 2019 he started sending reports to public tor-talk . About the Sybil attack related to monero attached the link above , you can here and here to see.
I also attach the work below about the identification and characterization of Sybil in the Tor network.
Here are some more links about infected relays and not only:
🦠Tor Network: Malicious Exit Relay and DNS Resolution
🦠Malicious Tor Network Servers Are Targeting Users’ Cryptocurrencies
🦠How malicious Tor relays are exploiting users in 2020
💥Types of relays(torproject)
💥Relay Search
#shizo #tor
|Leaked Chats Show LAPSUS$ Stole T-Mobile Source Code|
🔥KrebsOnSecurity разбирает полученные переписки LAPSUS$ в телеграмме(из частных каналов и переписок участников). Из которых можно узнать: количественный состав группы, никнеймы, нездоровый интерес к T-Mobile(White с помощью своего скрипта загрузил более 30 тысяч репозиториев исходников за 12 часов) и много другого можно почитать подробнее у Кребса.
⬇️На всякий случай прикрепляю документ ниже.
🔥KrebsOnSecurity analyzes the received LAPSUS$ correspondence in the telegram(from private channels and correspondence of participants). From which you can find out: the quantitative composition of the group, nicknames, unhealthy interest in T-Mobile (White downloaded more than 30 thousand source repositories in 12 hours using his script) and much more, you can read more from Krebs.
⬇️Just in case, I attach the document below.
#leak
🔥KrebsOnSecurity разбирает полученные переписки LAPSUS$ в телеграмме(из частных каналов и переписок участников). Из которых можно узнать: количественный состав группы, никнеймы, нездоровый интерес к T-Mobile(White с помощью своего скрипта загрузил более 30 тысяч репозиториев исходников за 12 часов) и много другого можно почитать подробнее у Кребса.
⬇️На всякий случай прикрепляю документ ниже.
🔥KrebsOnSecurity analyzes the received LAPSUS$ correspondence in the telegram(from private channels and correspondence of participants). From which you can find out: the quantitative composition of the group, nicknames, unhealthy interest in T-Mobile (White downloaded more than 30 thousand source repositories in 12 hours using his script) and much more, you can read more from Krebs.
⬇️Just in case, I attach the document below.
#leak
👍6😢1
This media is not supported in your browser
VIEW IN TELEGRAM
🤙Подписчик, да именно ты, пусть эти выходные пройдут у тебя так, как хочешь и желаю всего наилучшего.
🤙Subscriber, yes, it is you, let this weekend pass you the way you want and I wish you all the best.
🤙Subscriber, yes, it is you, let this weekend pass you the way you want and I wish you all the best.
❤18🔥2👍1
|LKM based rootkit|
🛡Только в образовательных целях
Шизо в свободное время балуется реверсом и работой с кернелом(конечно линух).
Ядерный(если говорить сухо - ring-0) руткит основанный на LKM. Интересный репозиторий, слежу за ним ещё с февраля 2022 года, когда появился.
Понравился репозиторий по нескольким причинам:
💾неплохо описан механизм работы руткита, как и вообще взаимодействие с ним
💾байпасс rkhunter(типо антируткит, который на самом деле не очень справляется с поиском ядерных модулей с вредоносной нагрузкой). Домашняя страница rkhunter и readme файл.
💾статья про создание руткита от автора руткита , где прям step by step разбирается этот процесс.
Руткит был протестирован на ядре 5.11.0-49-generic, Syscall interception mechanism section был полностью скопирован отсюда.
⬇️Приложу ниже работы про LKM, как про разработку загружаемых ядерных модулей,руткитов, так и обнаружение LKM - эксплоитов и про обнаружение ядерных руткитов.
🛡For educational purposes only!
Schizo in his spare time indulges in reverse and working with kernel(of course linux).
A kernel(ring-0) rootkit based on LKM. An interesting repository, I've been following it since February 2022, when it appeared.
I liked the repository for several reasons:
💾 the mechanism of the rootkit is well described, as well as interaction with it in general.
💾bypass rkhunter (like an anti-rootkit, which actually does not really cope with the search for loadavle kernel modules with a malicious load). Home page rkhunter and readme file.
💾 article about creating a rootkit from the author of the rootkit where this process is dealt with step by step.
The rootkit was tested on the 5.11.0-49-generic kernel, the Syscall interception mechanism section was completely copied from here.
⬇️I will attach below works about LKM, both about the development of LKM, rootkits, and the detection of LKM exploits and about the detection of LKM rootkits.
#rootkit #LKM #bypass
🛡Только в образовательных целях
Шизо в свободное время балуется реверсом и работой с кернелом(конечно линух).
Ядерный(если говорить сухо - ring-0) руткит основанный на LKM. Интересный репозиторий, слежу за ним ещё с февраля 2022 года, когда появился.
Понравился репозиторий по нескольким причинам:
💾неплохо описан механизм работы руткита, как и вообще взаимодействие с ним
💾байпасс rkhunter(типо антируткит, который на самом деле не очень справляется с поиском ядерных модулей с вредоносной нагрузкой). Домашняя страница rkhunter и readme файл.
💾статья про создание руткита от автора руткита , где прям step by step разбирается этот процесс.
Руткит был протестирован на ядре 5.11.0-49-generic, Syscall interception mechanism section был полностью скопирован отсюда.
⬇️Приложу ниже работы про LKM, как про разработку загружаемых ядерных модулей,руткитов, так и обнаружение LKM - эксплоитов и про обнаружение ядерных руткитов.
🛡For educational purposes only!
Schizo in his spare time indulges in reverse and working with kernel(of course linux).
A kernel(ring-0) rootkit based on LKM. An interesting repository, I've been following it since February 2022, when it appeared.
I liked the repository for several reasons:
💾 the mechanism of the rootkit is well described, as well as interaction with it in general.
💾bypass rkhunter (like an anti-rootkit, which actually does not really cope with the search for loadavle kernel modules with a malicious load). Home page rkhunter and readme file.
💾 article about creating a rootkit from the author of the rootkit where this process is dealt with step by step.
The rootkit was tested on the 5.11.0-49-generic kernel, the Syscall interception mechanism section was completely copied from here.
⬇️I will attach below works about LKM, both about the development of LKM, rootkits, and the detection of LKM exploits and about the detection of LKM rootkits.
#rootkit #LKM #bypass
👍1