mappy

190 posts

mappy banner
mappy

mappy

@0xmappy

Disfumblegaslighting... 🦀

Katılım Aralık 2019
415 Takip Edilen138 Takipçiler
mappy
mappy@0xmappy·
@PMV_InferX @jun_song @InferXai checked out InferX and the systems direction is genuinely interesting. How does BYOM actually work today? Can we deploy arbitrary Hugging Face/vLLM-compatible models? What exactly counts as a "model" in the $20/mo pricing?
English
1
0
1
310
송준 Jun Song
송준 Jun Song@jun_song·
If we ever figure out how to load ONLY the active params of an MoE into the GPU instead of the full weights, it's game over. Data centers would see a 100x efficiency boost. And we could literally run 1T models like Kimi locally on just 32GB VRAM. Yeah I know it's basically impossible right now, but who knows what the future holds. Let me dream.
English
91
39
848
72.4K
mappy
mappy@0xmappy·
@theonejvo 100 likes 7 hours later, makes sense, everyone is happy😝
English
0
0
1
58
Jamieson O'Reilly
Jamieson O'Reilly@theonejvo·
Cringe AF. Look how much BB platforms need you after slopping all that triage and then training off your submissions.
Jamieson O'Reilly tweet media
HackerOne@Hacker0x01

Calling all security researchers. @Anthropic’s bug bounty program is now public on HackerOne. The community has already helped strengthen Anthropic’s products through private testing. Now, anyone can help secure the future of AI. 🔐

English
4
0
17
2.9K
mappy
mappy@0xmappy·
@hrkrshnn @hacker_ @AnthropicAI yeah makes sense tbh, the infra/appsec surface is probably still way bigger rn what’s been the most interesting/frequent class of bugs so far by cantina on Anthropic program? I see 34 closed.
English
0
0
0
56
Hari
Hari@hrkrshnn·
@0xmappy @hacker_ @AnthropicAI I think the main one is traditional appsec, but they've separate programs for the model layer.
English
1
0
2
234
mappy
mappy@0xmappy·
@hrkrshnn @hacker_ @AnthropicAI What actually makes up most of the impactful findings here? Traditional appsec bugs or model-layer attacks like prompt injection/tool abuse? Just curious :)
English
1
0
2
228
Hari
Hari@hrkrshnn·
@hacker_ @AnthropicAI Coming from 7-figure crypto bounties, it's definitely a step down given the impact. But I'll take it. The amounts were higher in the private program IIRC.
English
2
0
3
805
nahcrof
nahcrof@nahcrof·
Just a pricing reminder (deepseek is ordered cache, input, output)
nahcrof tweet medianahcrof tweet media
English
5
1
78
5.2K
mappy
mappy@0xmappy·
@nahcrof Any idea how he measured? I would like to compare. I've got credits loaded up on both.
English
1
0
1
106
nahcrof
nahcrof@nahcrof·
@0xmappy About as similar as you could get without just using the official service itself, I had one person measure 95%
English
1
0
1
406
mappy
mappy@0xmappy·
Regarding the recent public disclosure vs private email debate… Here’s what I’ve actually experienced as a security researcher: - A company quietly removed its public self-hosted bug bounty program (that had safe harbour) and the ciso personally threatened me with “no safe harbour” after I submitted a valid report. (minimal testing was done) I’ve emailed hundreds of companies. a) Most open the email and completely ignore it. b) Some silently patch and ghost so they don’t have to pay a bounty. The worst part? Some of these companies run critical infrastructure and hold massive amounts of PII. Even when the security team replies, they’re friendly and responsive… right up until you ask, "Do you offer any bounty?" Full report submitted = instant ghosting. Companies that do have a bug bounty program still try to weasel out of paying by saying "this is out of scope", even when the vuln literally exposes their entire source code or production database. This piggybacking behaviour has to stop. So… should I just start calling out the names publicly? Is that how issues need to be fixed right now? Because the current system is broken #hackerone #bugcrowd #bugbounty
English
0
0
0
224
mappy retweetledi
H4x0r.DZ 🇰🇵
H4x0r.DZ 🇰🇵@h4x0r_dz·
To be secure in 2026 you have to shut down your bug bounty program on HackerOne. Lovable got hacked because HackerOne's incompetent triage team closed multiple valid vulnerability reports starting February 22, 2026 as "intended behavior." Poorly trained monkeys. Zero escalation to Lovable's security team. AI bots auto-closing critical findings. The result? Public project chat history and source code were exposed for MONTHS until a researcher was forced to go public. Two companies. Same platform. Same failure. Same lies. ClickUp. Lovable. Both breached because HackerOne buried critical reports while collecting your bounty fees. HackerOne is NOT a security partner. They are a liability. They close real vulnerabilities. They protect their own metrics over your data. They let researchers get attacked while they stay silent. Stop paying HackerOne to get hacked. lovable.dev/blog/our-respo…
H4x0r.DZ 🇰🇵 tweet media
English
51
96
879
89.4K
mappy
mappy@0xmappy·
@0xIlyy lmao so win+r now spins up Copilot every damn time.
English
0
0
37
6.3K
mappy
mappy@0xmappy·
@Zaddyzaddy For security related works as well? I've switched to opus 4.5 and it works great rn.
English
0
0
0
36
Z A D D Y
Z A D D Y@Zaddyzaddy·
If you’re using Opus 4.6 as your main driver for security-related tasks, you’re missing out.
English
1
0
2
512
OpenCode
OpenCode@opencode·
GLM-5.1 is now available in Go w/ Zero Data Retention
English
99
120
3K
197.5K
dax
dax@thdxr·
what if we gave you unlimited tokens for free and we also paid you
English
697
33
3.6K
244.5K