๐ Better inference efficiency, lower costs, broader access.
MiMo-V2.5 Series API pricing is now permanently reduced โ by up to 99% compared to previous pricing.
โจ Unified pricing across all context lengths.
MiMo Token Plans have also been upgraded:
โข 5โ8ร more usable tokens at the same price
โข Simpler and more transparent billing rules
๐ As a thank-you to current users, all current Token Plan credits will be fully reset.
๐ง MiMo-V2.5-TTS remains free for a limited time.
โฐ Effective May 26 at 6:00 PM PDT.
These improvements are powered by continued inference optimization and serving efficiency upgrades across the MiMo stack.
๐ ๏ธ Weโll also publish a detailed technical blog on the inference optimizations later โ stay tuned.
๐จ If you're hunting GraphQL bugs, this repo is a goldmine
๐ โawesome-graphql-securityโ is a curated list of tools, techniques & real-world resources for both attackers and defenders
From recon โ exploitation โ learning pathsโฆ itโs all here
๐ฃ Perfect for bug bounty hunters
๐ https://t.co/9ThzitmPkz
๐ Start exploring before others do
๐ฅ๐ฒ๐๐ฒ๐ฎ๐ฟ๐ฐ๐ต ๐ช๐ผ๐ฟ๐๐ต ๐ฅ๐ฒ๐ฎ๐ฑ๐ถ๐ป๐ด - ๐ช๐ฒ๐ฒ๐ธ ๐ญ๐ฎ, ๐ฎ๐ฌ๐ฎ๐ฒ
AI doing research, AI killing CTF
๐ค ๐ง๐ฒ๐๐๐ถ๐ป๐ด ๐๐ ๐ณ๐ผ๐ฟ ๐ฉ๐๐น๐ป๐ฒ๐ฟ๐ฎ๐ฏ๐ถ๐น๐ถ๐๐ ๐ฅ๐ฒ๐๐ฒ๐ฎ๐ฟ๐ฐ๐ต: ๐ฐ ๐๐ฝ๐ฝ๐ฟ๐ผ๐ฎ๐ฐ๐ต๐ฒ๐ & ๐ช๐ต๐ฒ๐ฟ๐ฒ ๐ ๐๐ฎ๐ถ๐น๐ฒ๐ฑ
If you can only read one thing this week, make it this article: https://t.co/NEXjJq0DNR.
๐ ๏ธ ๐๐๐ผ๐ธ๐ฒ๐๐๐ โ ๐ฆ๐ผ๐น๐๐ถ๐ป๐ด ๐๐ต๐ฒ ๐ฉ๐ฒ๐ป๐ฑ๐ผ๐ฟ ๐๐ฒ๐ฝ๐ฒ๐ป๐ฑ๐ฒ๐ป๐ฐ๐ ๐ฃ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ ๐ถ๐ป ๐ฅ๐
Reversing Java and C# applications just became a lot easier thanks to the SearchLight Cyber team (ex: Assetnote): https://t.co/B1jvGSZ5Us.
๐ง ๐ฆ๐ฎ๐๐ต๐ถ๐ธ๐ผ
Sashiko is an agentic Linux kernel code review system that monitors public mailing lists to thoroughly evaluate proposed Linux kernel changes. https://t.co/cFTkYMFozI.
๐ ๐๐ง๐ ๐ถ๐ ๐ฑ๐ฒ๐ฎ๐ฑ*
A good rant on the impact of AI on CTF... https://t.co/Q18G1JvX2m.
Combining WHOIS and cert data is underrated for recon. Find a target's registrant org, then search for certs issued to that same org - suddenly you're finding staging servers and internal tools on completely different domains
Here's *everything* you wanted to know about @rez0__'s AI workflow for hacking
HackerNotes TLDR for episode 166: https://t.co/NAgQXzzcVD
โบโ Claude Code skills should encode knowledge the model lacks and enforce deterministic workflows, not replace its creative reasoning
โบโ Build a fallback architecture in skills: primary tool โ SDK/library โ raw API, so the agent adapts when one layer fails
โบโ Structure your notes as a funnel: notes โ leads โ primitives โ findings โ reports to keep multi-session hacking organized
โบโ Run two parallel agents (one guided, one free-roaming) and cross-compare results to continuously improve your methodology
Rt for good luck ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐๐
Use this prompt for a thorough JS analysis:
You are an expert JavaScript reverse engineer and code analyst. I will provide you with
a JavaScript file. Perform a structured analysis with the following objectives:
## 1. High-Level Overview
- What is this code's purpose?
- Architecture pattern
- Key dependencies and frameworks used
- Execution flow: how does the code initialize and what is the main entry path?
## 2. Attack Surface & Endpoints
Extract and list ALL of the following in structured tables:
| Category | Examples to look for |
|-----------------------|---------------------------------------------------------|
| API routes/endpoints | paths, HTTP methods, route patterns |
| Parameters | query params, body fields, URL params, headers expected |
| Auth mechanisms | tokens, cookies, session logic, OAuth flows, API keys |
| WebSocket events | event names, channels, message schemas |
| External calls | fetch/axios URLs, third-party APIs, webhook targets |
## 3. Hidden & Interesting Artifacts
Look beneath the surface for:
- Hardcoded strings: URLs, IPs, hostnames, ports, internal service names
- Environment variables referenced (process.env.*)
- Database schemas, table/collection names, field names
- Role names, permission levels, feature flags
- Debug/admin/test routes or commented-out functionality
- Error messages that reveal internal structure
- Regex patterns (what are they validating/extracting?)
- File system paths (uploads, logs, configs, temp dirs)
## 4. Data Flow Map
Trace how user input moves through the code:
- Entry point (where does external data come in?)
- Transformations (parsing, validation, sanitization, or lack thereof)
- Storage (where does it end up: DB, file, cache, external service?)
- Output (what gets returned/rendered to the user?)
## Formatting Rules
- Use tables for structured data (endpoints, params, env vars)
- Use code snippets with line references for each finding
- Flag anything that seems intentionally obscured or unusual
- If the code is minified/obfuscated, note patterns and attempt to
identify the original framework or library
---
Here is the code:
<YOUR_CODE_HERE>