Fiddy (@Number_055) profile picture

You can always to steal from AAA corporations. It is always morally correct. Twitter bullshit fucked me off. Now I repost art.

Upside-Down Town
Joined August 2017
Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)Photo by Fiddy (@Number_055)
Today is Steve Irwin day. One of the greatest humans to ever grace this planet
43
321
14
2,722
77,124
the image of Magnus holding a carrot makes me think of this
El legendario Sportacus, Magnús Scheving, está cumpliendo 62 años.
34
2,317
5
17,740
93,344
>DLC being regarded as absolutely gigantic again >2026 release date now removed and no clear release window has been given >Only getting vague information from Nintendo about it
Dentro da mídia física de Silksong pro Switch 2 vem esse folder aqui. Duas coisas me chamaram a atenção: >os caras já estão chamando Sea of Sorrow de ''giant expansion'' >não tem mais menção de sair em 2026 O ciclo está se repetindo, Team Cherry se empolgou demais e essa DLC vai acabar virando um jogo novo kkkkkkkkkkkkkk
105
4,869
68
42,344
608,275
my vent art
158
1,330
125
18,979
387,077
Speed art of my favorite #pokemon #lucario
10
541
3
7,616
52,160
Fiddy retweeted
3
221
1,730
8,869
Fiddy retweeted
ralsei in my new hyperrealistic style
194
11,390
82
121,338
813,294
“The first time I watched you sleep.” #StolitzWeek2024 #Stolitz #HelluvaBoss
28
919
11
6,061
82,471
Fiddy retweeted
Sora needs to file a re:straining order
5
10
303
#HelluvaBoss #stolitz 블리스톨 부비부비~🫂🫂
185
3
1,155
9,770
45
1,422
32
42,479
523,850
乾かす
1
148
1
1,604
11,129
Fiddy retweeted
🚨 BREAKING This guy deleted his entire Steam game library during a mental health episode. He contacted Steam Support asking if they could restore his library or at least provide a list of the games he previously owned. Steam Support restored his entire game library
673
2,105
355
45,680
2,364,284
Replying to @skinwaste
i’ve heard enough, give gaben another yacht
13
62
2
7,193
197,806
>2027 >wake up and go to bathroom >Iran has hacked the smart toilet servers, cant flush >wander to kitchen >A North Korean cyberattack has taken my smart coffee machine offline >”ok I’ll just boil water on the stove” >smart sink bricked by Russian DDoS >smart stove offline because I forgot to pay my stove subscription again >fml >”maybe a movie will distract me” >try to turn on smart TV >I’ve been banned from my smart remote bc it overheard me criticizing Israel >mfw
164
3,377
93
30,799
448,501
Fiddy retweeted
Trick or treat!! #casualtiesunkown
23
794
1
9,698
55,252
Man, what the hell is this @PonyConHolland
11
51
2
364
6,254
Fiddy retweeted
hmmm...
673
8,995
427
117,369
3,737,323
Crazy 72 hours in security. Three major incidents dropped back-to-back: eMudhra, PingCAP (TiDB Cloud), and PHP. Here is the short version of what happened and who got hit. 1. eMudhra (Trusted CA compromise) eMudhra generated 8 intermediate CA certificates in April 2025 (cross-signed by Sectigo). A bug in their HSM key-wrapping test script created a second set of P-384 keys where the private keys were single-byte numbers under 256. Operators picked the wrong key labels and signed them into real CA certs. One of the intermediate CA private keys was literally the number 4. The other seven: 56, 66, 115, 155, 156, 230, 237. Three weeks later (May 2025), their CRL signatures started failing because the CRL signer was using the real keys instead of the weak ones. Instead of asking why the keys didn't match, someone switched the CRL signer to the weak keys and closed the ticket. • Browsers are safe: Chrome, Firefox, Apple, and Microsoft already blocked them, and zero rogue certs hit CT logs. • Servers are not: curl, Python (certifi), Go binaries, and Docker base images don't check CRLs. Update ca-certificates, certifi, and Go (1.27.3 / 1.26.10). • 10-second check on any server: curl dv-g3b-emudhra.we-have-a-pro… (TLS error = safe. 200 OK = still vulnerable.) 2. PingCAP / TiDB Cloud (10.6 TB breach) Attackers found GCP and Azure credentials committed inside PingCAP's own repos. They set up a replication feed of TiDB Cloud's production control plane and exported the entire database every 6 hours for 22 straight days. 88 full exports, zero alerts. 200 GB is already out on torrents. Beyond the 413 private repos and 20.6M customer SQL queries logged from their web SQL Editor, PingCAP engineers were pasting customer secrets into Jira tickets. Who is affected in the leaked records: • Live credentials exposed in support tickets: - Pinterest: AWS keys for their pingcap-logs S3 bucket - CardX / Silverlake (NPCI-linked env): AWS admin key in a backup log with full access to 258 external S3 buckets - DeBank: 38 presigned S3 URLs - An unnamed AI/dev platform: a 314 MB slow-query log attached to a ticket containing 8,027 live customer secrets (an AWS root key, a GitHub admin PAT over 1,701 repos, 7,485 AWS STS tokens, and 192 OpenAI/Anthropic/Gemini keys) • Tenants with infra metadata, VPC CIDRs, app-server IPs, or contract pricing exposed: - Tech: Atlassian, Databricks, Airbnb, Baidu, LINE, Nylas, Persona, PatSnap - E-comm & Travel: Booking.com, Shopee, Flipkart, Mercari, ZOZO, AEON, Delhivery, Klook - Gaming: Capcom, Square Enix, Konami, Bandai Namco, Cygames, Colopl, DMM - Finance: PayPay, SoftBank, SBI, SB Payment Service, Fujitsu, TOPPAN, Bank of China, China Life - Crypto: Bitget (said only public trade logs were on it and they already left), Pionex, DigiPlus, NFTscan, Chainbase • Developer profiles leaked (from a purchased reo.dev table in PingCAP's BigQuery): - 24,900 personal emails + GitHub/LinkedIn profiles of engineers at Tencent (3,327), Huawei (2,726), ByteDance (2,475), AIG (2,140), Mastercard, Flipkart, and bKash. If you use TiDB Cloud: rotate your console API keys, DB passwords, and anything you ever pasted into a support ticket. 3. PHP "PHP2Shell" (CVE-2026-109618 & CVE-2026-109619) Two CVSS 9.2 pre-auth RCEs leaked yesterday ahead of today's 14:00 UTC patch. Public writeups trace it to a heap Use-After-Free in PHP's native C multipart/form-data session upload-progress handler (ext/session/session.c). Because C-level multipart parsing runs before line 1 of index.php: • App auth, Laravel/WordPress middleware, and file_uploads = Off do not stop it. • Only PHP 8.2–8.5 get official patches today (59% of PHP servers on Shodan are on EOL <= 8.1). • Until you patch php-fpm: lock php_admin_flag[session.upload_progress.enabled] = off and block unexpected multipart requests at Nginx/Apache/Cloudflare.
105
1,414
179
9,455
991,719
New contender for the greatest GTA mod of all time It's called ViceBounce, and it causes all the game assets to bounce to the beat You can pick any song you like, just provide it with an mp3
331
5,718
336
57,732
1,699,756