Pinned Tweet
#PowerShell Pro Obfuscator & Virtualizer
✔️Advanced obfuscations
✔️Virtualization
✔️Finite-state automata
✔️Self-defending against decompilation
✔️Anti-debugging
✔️Decoys
✔️API for #csharp #rust #python #js #php
✔️Win / Lin UI & CLI
pelock.com/powershell-pro…
#redteam #hacking
✔️Advanced obfuscations
✔️Virtualization
✔️Finite-state automata
✔️Self-defending against decompilation
✔️Anti-debugging
✔️Decoys
✔️API for #csharp #rust #python #js #php
✔️Win / Lin UI & CLI
pelock.com/powershell-pro…
#redteam #hacking
4
8
85
4,344
PELock retweeted
Nissan sued a computer repairman for $10,000,000 to take the Nissan․com domain.
His legal last name was Uzi Nissan.
He refused to fold, spent $3,000,000 fighting them in federal court for 8 years, and won.
This is the story of Uzi Nissan and why a $20B car giant still can't 994
- Uzi Nissan emigrates from Israel to Raleigh, North Carolina
- opens a small auto repair shop in 1980 using his family surname
- launches Nissan Computer Corporation on May 14, 1991 selling PCs and servers
- registers Nissan․com on June 4, 1994 for $70 while the automaker barely touches the web
December 10, 1999
- Nissan Motor Co. realizes a North Carolina PC shop owns their exact domain
- instead of paying his asking price, the automaker files a $10,000,000 federal lawsuit for cybersquatting
- Uzi refuses to back down and turns the homepage of Nissan․com into a public archive of their legal threats
1999-2007
- the court battle drags on for 8 years across district court, the Ninth Circuit, and a Supreme Court petition
- Uzi spends over $3,000,000 in legal fees and takes out two mortgages on his home
- federal judges rule a corporation can't strip a man of a domain built on his own birth name
July 2020 - Today
- Uzi Nissan passes away from COVID-19 in July 2020 at age 68
- when thieves hijack the domain after his death, a federal judge orders Nissan․com returned to his family estate in April 2024
To this day, Nissan Motors is forced to use NissanUSA․com.
If you type Nissan․com into your browser right now, you still don't get a car dealership.
You get a memorial to the computer repairman who beat a multinational giant over his own last name.
His legal last name was Uzi Nissan.
He refused to fold, spent $3,000,000 fighting them in federal court for 8 years, and won.
This is the story of Uzi Nissan and why a $20B car giant still can't 994
- Uzi Nissan emigrates from Israel to Raleigh, North Carolina
- opens a small auto repair shop in 1980 using his family surname
- launches Nissan Computer Corporation on May 14, 1991 selling PCs and servers
- registers Nissan․com on June 4, 1994 for $70 while the automaker barely touches the web
December 10, 1999
- Nissan Motor Co. realizes a North Carolina PC shop owns their exact domain
- instead of paying his asking price, the automaker files a $10,000,000 federal lawsuit for cybersquatting
- Uzi refuses to back down and turns the homepage of Nissan․com into a public archive of their legal threats
1999-2007
- the court battle drags on for 8 years across district court, the Ninth Circuit, and a Supreme Court petition
- Uzi spends over $3,000,000 in legal fees and takes out two mortgages on his home
- federal judges rule a corporation can't strip a man of a domain built on his own birth name
July 2020 - Today
- Uzi Nissan passes away from COVID-19 in July 2020 at age 68
- when thieves hijack the domain after his death, a federal judge orders Nissan․com returned to his family estate in April 2024
To this day, Nissan Motors is forced to use NissanUSA․com.
If you type Nissan․com into your browser right now, you still don't get a car dealership.
You get a memorial to the computer repairman who beat a multinational giant over his own last name.
422
978
18,403
2,116,615
PELock retweeted
Holy sh*t. Claude Code just found a hidden chip inside my Chinese power bank from Guangzhou. Every time I charged my iPhone, it quietly copied the whole phone…
It also read our saved Wi-Fi password off my iPhone, got onto our home network and sent everything to a server.
I airport kiosk there 3 weeks ago. No brand, 30,000 mAh on the label, and it felt heavy.
The first time I plugged in, the screen asked "Trust This Computer?". I tapped Trust without thinking and went on with my day. That one tap gave it access to everything.
This morning I finally set up Claude Code to warn me when any device starts reading my files. An hour later, 10 seconds into charging, the screen filled with yellow warnings, then red ones: data was moving when it should only be charging.
I asked Claude Code what was going on. My phone saw the power bank as a small computer with 64 GB of storage and its own internet connection.
A USB cable has wires for power and wires for data, and a normal charger only uses the power ones. This one used both, and it had already copied all of this:
→ /device → IMEI and serial number
→ /contacts → 1,206 numbers
→ /apps → every app I have, including my 2 bank apps
→ /photos → 3,912 pictures, my passport among them
→ /wifi → our network name and its key
→ /wife's iPhone → her photos too, she charged from it twice and tapped Trust too
Each time we plugged in, it used that key to get online and send out the new files:
sends to → 47.***.***.12
uploads → 19 in 3 weeks
last one → last night at 2:14, while we slept
I pulled the cable right away. Then Claude Code blocked that address on our router and walked me through changing the Wi-Fi password and the logins for my bank apps.
I had it opened at a repair shop, and what was inside is in the first comment. A 30-second check for your own is in the second one. Save this and test every power bank in your house today.
It also read our saved Wi-Fi password off my iPhone, got onto our home network and sent everything to a server.
I airport kiosk there 3 weeks ago. No brand, 30,000 mAh on the label, and it felt heavy.
The first time I plugged in, the screen asked "Trust This Computer?". I tapped Trust without thinking and went on with my day. That one tap gave it access to everything.
This morning I finally set up Claude Code to warn me when any device starts reading my files. An hour later, 10 seconds into charging, the screen filled with yellow warnings, then red ones: data was moving when it should only be charging.
I asked Claude Code what was going on. My phone saw the power bank as a small computer with 64 GB of storage and its own internet connection.
A USB cable has wires for power and wires for data, and a normal charger only uses the power ones. This one used both, and it had already copied all of this:
→ /device → IMEI and serial number
→ /contacts → 1,206 numbers
→ /apps → every app I have, including my 2 bank apps
→ /photos → 3,912 pictures, my passport among them
→ /wifi → our network name and its key
→ /wife's iPhone → her photos too, she charged from it twice and tapped Trust too
Each time we plugged in, it used that key to get online and send out the new files:
sends to → 47.***.***.12
uploads → 19 in 3 weeks
last one → last night at 2:14, while we slept
I pulled the cable right away. Then Claude Code blocked that address on our router and walked me through changing the Wi-Fi password and the logins for my bank apps.
I had it opened at a repair shop, and what was inside is in the first comment. A 30-second check for your own is in the second one. Save this and test every power bank in your house today.
571
2,483
9,326
1,387,184
Aural Planet - Lightflow (1997), one of my❤️#demoscene albums ever. Full album at:
⏯️youtube.com/watch?v=xr5U2w…
#electronicmusic
⏯️youtube.com/watch?v=xr5U2w…
#electronicmusic
0
0
3
92
PELock retweeted
Modern Virus Writing Guide Ep.1: Intro to Virus Writing in x64 Assembly maltrak.com/blog/modern-vi…
1
13
58
2,397
New #Delphi decompiler. Decompile VCL applications written in Delphi 3–13 or built with C++Builder, for Win32 and Win64, into Delphi-like Pascal.
de-decompiler.com
#malware #reversing #hacking #antivirus #programming
de-decompiler.com
#malware #reversing #hacking #antivirus #programming
5
34
236
8,137
PELock retweeted
Executing Shellcode in an Isolated vCPU
New Medium post, today we are going to explore executing shellcode inside an isolated virtual CPU using the Windows Hypervisor Platform API, a technique that runs x64 code in a hardware isolated VM context
medium.com/@s12deff/execu…
New Medium post, today we are going to explore executing shellcode inside an isolated virtual CPU using the Windows Hypervisor Platform API, a technique that runs x64 code in a hardware isolated VM context
medium.com/@s12deff/execu…
1
14
134
3,763
PELock retweeted
Looking through my photos I realized that I am now ready to write my article about SCSI and why it sucks. Maybe I shouldn't have waited 24 years to write that...
13
2
59
1,717
Hash Calculator app, 49 algos (MD5, SHA, CRC etc.), quick search, favorite algos, hex/text/file input, no bs
play.google.com/store/apps/det…
#programming #hacks #hacking #CryptoSecurity
play.google.com/store/apps/det…
#programming #hacks #hacking #CryptoSecurity
0
1
7
408
PELock retweeted
Sports science, psychedelics and shamanism 🤩 with the legend @joerogan Experience #2568 - Ross Edgley youtu.be/IsCQwOXi6XI?si…
0
1
13
4,091
Kalkulator Lokaty to polska aplikacja na Androida, umożliwiająca obliczenie odsetek z lokaty, biorąc pod uwagę podatek Belki, bonus, liczy co do grosza, tak jak bank
play.google.com/store/apps/det…
#bank #lokata #lokatabankowa #pieniadze @mBankpl @Cashlesspl @NestBank @velobank @PKOBP
play.google.com/store/apps/det…
#bank #lokata #lokatabankowa #pieniadze @mBankpl @Cashlesspl @NestBank @velobank @PKOBP
0
0
3
243
PELock retweeted
Bro is laying off employees with one hand and posting job openings with the other.
56
192
3,015
76,220
PELock retweeted
Standard IEEE 754 od dekad dominuje w świecie liczb zmiennoprzecinkowych, oferując powszechne wsparcie sprzętowe i programowe. Jednak dynamiczny rozwój sztucznej inteligencji i uczenia maszynowego wymusił poszukiwanie bardziej wydajnych rozwiązań: programistamag.pl/download/
0
1
0
107
PELock retweeted
Since the @Apple Bug Bounty Program is by far the worst program I've ever hacked on, I am going to be dumping all of the data/POCs/report write ups etc for everything found during the 4 months of hacking them. This will include POCs for vulns that didnt meet their bar for a bounty so wasnt reported to them, so you may be able to find ways to escalate some of them. Ill be uploading the data all this weekend.
131
355
7,643
533,841
