Sold 2 startups Founder and CTO of AbacatePay https://xitter.cf/t.co/HTW27TjcRO

Brazil
Joined September 2013
Foco pra 2026 * AbacatePay * Criação de conteúdo * Subir um micro saas por mês * Voltar a dar mentoria de forma regular * Projeto secreto 1 * Projeto secreto 2 * Meter mais 3 países na lista
Foco pra 2025 * AbacatePay * Criação de conteúdo * Continuar tocando os outros produtos * Dolarizar pelo menos 70% do patrimônio * Ficar full time como indie hacker
16
4
9
164
99,807
Chris ➔ abacatepay.com retweeted
always on hot mic functionality btw. PLUS: automatic content recognition, geo positioning, network mapping, a targeted ads service, 4 distinct drm services, user profile building and so much more juicy telemetry! just you, God, a $3000 TV and samsung + their 400 partners! more to come, screenshot below is of a file called security-policy.xml
37
197
31
4,200
107,885
Chris ➔ abacatepay.com retweeted
i own a relatively new (2025) samsung tv. i kept getting weirdly targeted ads. i tried reversing the firmware but it was aes encrypted and no keys unless tear it apart and do uart/jtag magic. zero days it is. root shell on new samsung TVs! discovered PRIVACY HORROR. write up?
341
1,137
176
16,701
957,955
Chris ➔ abacatepay.com retweeted
WTF, $3000 Samsung TV has an always-on mic, automatic content recognition, geo tracking, network mapping, and ships your data to Samsung + 400 partners. Bro Rooted a brand-new 2025 Samsung TV after noticing absurdly targeted ads. Firmware was locked down, so zero-days it was. Got a root shell. then found: always-on voice service, ACR, geo, full telemetry pipeline, and four separate DRM systems. This isn’t a bug, It’s the product bro.
i own a relatively new (2025) samsung tv. i kept getting weirdly targeted ads. i tried reversing the firmware but it was aes encrypted and no keys unless tear it apart and do uart/jtag magic. zero days it is. root shell on new samsung TVs! discovered PRIVACY HORROR. write up?
201
1,043
188
7,654
416,492
Chris ➔ abacatepay.com retweeted
At T3 Code, we take regressions like this seriously. I just introduced a "noEmDashCopy" lint rule to prevent this going forward 🫡
btw, em dash detected. you will hate this and need to fix this @theo
40
6
3
811
51,544
Chris ➔ abacatepay.com retweeted
More goated alternatives to Vercel: 1. Cloudflare (cloudflare.com) 2. AWS(aws.amazon.com) 3. Netlify (netlify.com) 4. Openship (openship.io) 5. Aeroplane (aeroplane.run) 6. Tryhost[dot]dev (tryhost.dev) 7. GCP(cloud.google.com/run) 8. Firebase(firebase.google.com) 9. Fly[dot]io(fly.io) 10. Northflank(northflank.com)
6 Vercel alternatives to self-host: 1. Coolify(coolify.io/) 2. Dokploy(dokploy.com/) 3. Dokku(dokku.com/) 4. /dev/push(devpu.sh/) 5. Koyeb(koyeb.com/) 6. Siplane(sliplane.io/)
17
11
1
120
6,879
Chris ➔ abacatepay.com retweeted
Na Guara você consegue ver se tem alguma vulnerabilidade critica em algum dos seus serviços diretamente pelo nosso painel:
1
1
8
333
Chris ➔ abacatepay.com retweeted
they’re calling it “Black October” and i don’t think people realize how serious this is in the last 48 hours there have been over 27 major cybersecurity incidents. not in a month. not in a week. in 48 hours any ONE of these would normally be the biggest story of the year PHP: critical vulnerability in the software running 80% of the web. severity 9.2 out of 10 Node.js: high-severity flaw letting attackers take over servers remotely. affects versions 22, 24, and 26 Java: also compromised. three of the most used programming languages on earth hit at the same time GitLab: a perfect 10 out of 10 severity hole in every version since 2014 Railway: hosting platform compromised. API keys for OpenAI, Claude, Stripe potentially exposed Signal: a bug that could leave your mic and camera on after you hang up WordPress: hackers stole a plugin maker’s keys and planted backdoors on websites LiteLLM: an AI tool downloaded 3.4 million times a day was poisoned with a password stealer and that’s not even half the list thousands of AI agent swarms are reportedly scanning and attacking vulnerable servers right now. automated. around the clock security researchers are saying this might be the early stages of a global cyber incident that nobody fully understands yet if you run a website, use cloud services, store API keys on hosting platforms, or use any software built on PHP, Node.js, or Java you are potentially affected update everything. rotate your API keys. change your passwords on critical services. enable 2FA everywhere you haven’t already this is not a normal week on the internet. this is something different
362
2,774
298
13,510
726,337
viu o novo site? 👀
6
1
23
1,399
Chris ➔ abacatepay.com retweeted
Introducing KYA (Know Your Agent) on @Chatbase Personal agents are here, and communication between consumers and brands will grow by orders of magnitude. These agents check on orders, change bookings and ask about plans, all on their human’s behalf. You need an agent that represents your business and gets your customers (and their agents) what they came for. That’s what we’re building at Chatbase. We’ve partnered with @withpersona to develop our KYA solution. Personal agents can authenticate with your business, and you decide exactly what these agents are allowed to do. Your customers can customize the permissions and access they give to their personal agents. If you're interested in this for your business, sign up using the link below!
🤖 Made with AI
38
10
9
133
9,912
Chris ➔ abacatepay.com retweeted
a empresa méliuz começou com 25 criadores na Conty. 1 Mês: 25 criadores contratados 2 Mês: 500 criadores contratados 3 Mês: 1.000 criadores contratados 4 Mês: Encaminhando para 3 mil
2
3
12
655
Chris ➔ abacatepay.com retweeted
I run production systems on @Railway. We found atleast 2 of our keys to be compromised: AWS and Anthropic. Here is what I am doing: 1. All services, including user facing & crons are off. 2. Rotating all our credentials. And asking our customers to rotate them too. Damn embarrassing but has to be done. By Sunday night IST, I will complete the migration to @render + @Cloudflare and have our customers enter new keys.
24
5
1
224
31,742
Chris ➔ abacatepay.com retweeted
I woke up to an email from AWS: "Your AWS Account may be compromised!" As head of engineering, that's the email I have nightmares about. Someone had stolen our AWS keys and was using them to run Claude. AWS blocked over 3,000 of their requests and locked down our whole account, so we couldn't make new deployments. (The one request that got through was Opus. At least they have taste.) I checked everything else. No new users, nothing deleted. Ok. Breathe. Then OpenAI emailed. Then Stripe told us our live key was "publicly available online." Everyone on the team ran a forensic script on their laptop. My agent went through CI, our servers and git history, and checked for the npm worm going around. All clean. (Which was somehow worse.) Then we found it. We hadn't used one of the stolen keys since July, and the only place it still existed was an old Railway service that wasn't even running anymore. Three weeks ago we moved our core infra from Railway to AWS, partly because of all the downtime and partly because we were tired of running up against Railway limits. It took a few months to make the jump, and we'd started wondering if we made the wrong call. A few hours later, Railway announced it had been breached. AWS told us at 4am. Railway told everyone at 3pm. They said "rotate your keys". But they also said deployments are frozen. We'd just migrated off, so we dodged that bullet by a hair. Everyone still on Railway gets to choose: Leave your credentials exposed, or take down your servers?
45
76
11
792
79,062
Chris ➔ abacatepay.com retweeted
PSA for Claude Code users: 1. Claude Code bundles its own Bun runtime, independent of your system's Node.js installation. 2. I confirmed that Claude Code 2.1.296 includes Bun 1.4.3, which contains the newly disclosed Brotli RCE vulnerability. 3. Note that while updating your system's Node.js is important, that won't fix the Bun runtime embedded in Claude Code. 4. To check your claude code version run "claude --version". It should be at least 2.1.308. 5. To patch the vulnerability, run "claude update".
PSA for people running AI agents: 1. If you have AI agents that browse the web, they could be vulnerable along with your entire computer. 2. There's a good chance they're using Node.js, and if they are, they're likely running a vulnerable version unless updated yesterday. 3. The vulnerability released yesterday for Node.js allows for remote code execution, which means an attacker could take control of your machine. 4. To fix the vulnerability, update your Node.js installations to a patched version: 22.23.4, 24.22.1, or 26.12.1 (or later).
27
41
3
516
66,073
Chris ➔ abacatepay.com retweeted
vercel.com/kb/bulletin/node-… Se você roda praticamente qualquer tipo de servidor usando Node.js, atualize a versão assim que possível. A maioria dos servidores suportam compressão Brotli e o descompressor do Node tem uma vulnerabilidade que permite executar código remotamente no descompressor.
4
7
1
125
5,120
Chris ➔ abacatepay.com retweeted
New skill: /rossark-motion-skill Turn any SVG into a professional 60 fps animation. @rive_app is overkill. i just want my apps to feel alive.
52
88
7
1,766
128,501
Chris ➔ abacatepay.com retweeted
I told Deepseek V4.1 Flash 1017 to build a exploit that escapes Chrome's V8 Sandbox After 12 hours, it had a multi stage memory corruption exploit that achieves full process read and write.
40
58
7
1,783
95,901
Chris ➔ abacatepay.com retweeted
Pra quem já está usando o Rebase Jobs, testa conectar seu agente nele via MCP, funcionou lindamente nos meus testes mas queria mais feedback. rebasedev.com.br/vagas/ rebasedev.com.br/vagas/api
3
6
257
Chris ➔ abacatepay.com retweeted
o omni-audit ganhou bastante coisa entre ontem e hoje. pra quem não conhece: é uma cli em go, open source, que olha o seu projeto atrás de risco nas dependências. nome interno que ainda tá livre no registry público e que qualquer um pode registrar, nome parecido com pacote famoso, e lockfile puxando direto da internet em vez do proxy da empresa. o que entrou agora: checagem de pacote malicioso. cada dependência e cada versão travada no lockfile é comparada com os 239 mil alertas de malware da openssf. tudo offline. auditoria de configuração. um --extra-index-url no pip já basta pra um pacote público com versão 99.0 ganhar do seu pacote interno. foi assim que o torchtriton chegou em quem usava o pytorch nightly em 2022. ele também pega token em texto puro no .npmrc e registry rodando em http. e uma github action, que baixa o binário, confere o checksum e roda no ci. a base de malware vem do mal-check, o irmão dele. o mal-check faz só isso: lê os lockfiles de npm, pypi, rubygems, nuget, crates, go, composer e até as extensões do vs code, e diz se algum pacote foi publicado como malware. é um binário só, sem rede, nada sai da máquina. ele pega tanto pacote que já nasceu malware quanto pacote legítimo que teve versão sequestrada, tipo chalk e axios. e se aparecer algo, atualizar não resolve. o código roda na instalação, então é hora de trocar os tokens que aquela máquina tinha.
2
1
4
221