News for hackers. Stuff that matters.

pbear2k23

Re:Zero-day Bitcoin OOM crash on Tuesday October 22, 2024 @08:37AM (#41913620)
tl;dr https://pastebin.com/raw/qr8XWFkR - you f*cking ping faster than it pongs. this wasn't discovered until recently. sad.

i put this together. it also contains a mode for CVE-2023-33297 ('headers') which was recently patched - although i wasn't given credit because i have haters @ bitcoin-core and blockstream. they kinda run the show now. i'm even banned from contributing to the bitcoin-core github. much decentralization.

how to reproduce the vulnerability yourself:

1. install bitcoin

2. ./bitcoind

3. edit your ip into attack.go: https://pastebin.com/raw/qr8XWFkR

4. save attack.go

5. snap install go --classic

6. go build attack.go

7. ./attack

8. slow oom crash - enjoy the fireworks

screenshot: https://i.imgur.com/DA80ORS.png

happy to answer any questions

MD5 Blockchain

can someone try to debunk this? (without "why?")in an md5 blockchain system the previous block of a chain is hashed by 7 md5 hashes which act as shards for anti-collision purposes and single concatenated hash strings as prev_block's value.this hash string comprised of 7 md5 hashes which act a salt for the md5 word puzzles that are necessary for a miner to solve in order to publish...

( Read More... | no comments | on HN )
Re:New Anti-Deepfake Strategy on Sunday January 14, 2024 @06:46AM (#38989588)
that's... not at all a solution. "just use onfido" doesn't solve deepfakes. too much friction isn't true whatsoever it would just take some solid coders. and finally i don't suggest that anyone work with onfido. they fleeced me out of a $10k deposit in 2018 for kyc services that were falsely advertised as deeply international only for us to realize that wasn't the case at all. no refund. no partial refund. no access to credits anymore. $10k gone because onfido is shady.
Re:New Anti-Deepfake Strategy on Sunday January 14, 2024 @04:43AM (#38988953)
i came up with this. it has a lot of moving parts but it's viable. i understand the idea of "why not just publish transcripts in advance on whitehouse.gov" and the answer is because there are too many points of failure, like the risk of shells, rogue actors, dns hijacking, ddos, etc.

these issues are alleviated by multiple blockchains running byzantine fault tolerance against speeches that are monitored and authenticated by public facing figures both beforehand and during the live broadcast.

i know it seems complicated - but it needs to be.

happy to answer any questions if they aren't rude. i understand that this is a lofty proposal and the natural reaction is a knee-jerk "yeah ok" - but give it a read. play with it in chatgpt. this is about viability and computer science theory more so than a tangible effort in establishing a funded operation.

tl;dr blending bleeding edge technologies together to 360 noscope deepfakes.

Re:0day Bitcoin P2P Crash (OOM) on Monday January 01, 2024 @04:28PM (#38835514)
this is being privately disclosed - but i found it and attest to its authenticity. i'm happy to answer some, but not all, technical questions.
Re:New Bitcoin DoS Exploit Code on Monday December 18, 2023 @03:54PM (#38688115)
if for instance the attack program was routed through tor i don't see why it wouldn't work at damaging capacity with a modified script
Re:"Patched" Bitcoin DoS Still Vulnerable on Saturday December 16, 2023 @09:01AM (#38664246)
Re:CIA's Telegram Hijacked on Wednesday October 18, 2023 @01:39AM (#37925188)
>right, because so many people are typing in the incorrectly shortened URL instead of clicking on the link

it was clickable - and yes they dodged a bullet. the channel could have been perfectly reproduced, made to look real, and then used to intercept western intelligence. there was no manual "typing" of links

Re:CIA's Telegram Hijacked on Wednesday October 18, 2023 @01:12AM (#37925046)
was me if anyone wants details - but it's pretty simple. not a hack. registered an available username so that opposition ic groups couldn't do the same - they could have dressed it up in a visually identical way and intercept western intel. it's just an intelligence failure. those aren't new - nor is this really even that big of a deal - imo - it just could have hypothetically been a big deal - and i don't really care for hypotheticals

https://x.com/123456/status/1714496858754576516?s=20

Re:Doxing Has Become Spooky on Tuesday October 10, 2023 @11:22AM (#37833239)
so you didn't read it but are sharing meta-feedback?
i discovered the issue if anyone would like for me to unpack anything.

content snippet + attack code:

the takeaway from pad vs bitcoin is that a botnet can remotely charge public listening node operators thousands of dollars.

that would snowball into a mass exodus of public nodes until all that remained were millions lost unexpectedly by thousands of node operators - and a network centralized by entities able to weather the cat 5 hurricane of upstream overage fees, like:

1. mining pools

2. exchanges

3. hnwis

4. governments

effectively centralizing the network and causing countless millions in damages. the ethos of bitcoin and the financial survival of its operators are at stake.

example attack code: https://github.com/visualbasic6/drain

Re:Tumblr Phishing Attack (2011) on Saturday October 07, 2023 @06:39PM (#37806130)
don't mind me - nonchalantly taking credit for various nonsense i did as a kid. way past the statue of limitations - and hopefully found interesting to someone
Re:Phishing 2FA 25 years ago on Saturday October 07, 2023 @06:28AM (#37800551)
> Taking over AOL “int” accounts was actually considered pretty basic at that time.

to the skillful it was considered basic - for sure. there was a lot of collaborative intelligence in the aol "hacking" scene, though. and you could do a lot on an int. even reading internal aol emails often returned a treasure trove of new tools and information

>The best was when Gosh

legend

>was fun to DoS entire rooms of users offline

yeah that could be done to older computers just by scrolling without rate limits as you mentioned. semi-related - i once found a dos in skype that made use of skype4com.dll to change your display name hundreds of times per second. if you had more memory on your computer than your contacts did you could dos hundreds of people at once. i remember it reminding me of some corny aol "hack"

Older »