Offensive cyber is our thing.
McLean, VA
Joined January 2025
- Tweets1.9K
- Following296
- Followers5.3K
- Likes5.2K
Pinned Tweet
Our business model is this:
- Attract the very best vulnerability researchers and exploit developers in the world to join our company. This mostly revolves around junior engineers with raw talent/extremely high IQ. We don’t care if they have a college degree/industry experience or if they are total recluse-types who never want to attend some stupid “team building event” or whatever.
This is largely an individual sport. And we want the Roger Federer(s) and Novak Djokavic(s) to work for us. We will hone their skills beyond what would be otherwise possible and polish them into absolutely deadly weapons.
- Pay them so well (including serious equity), and task them with working on things so cool, that they would never even want to take an interview for a job at another firm (think Renaissance Technologies in the hedge fund world, but for computer network exploitation). We want to make these people very rich—which almost never happens to people with these skills in this industry. The only tradeoff is that they will have zero fame or public recognition, and they have to be okay with that (fame is overrated anyway)
- Build the resulting primitives into the most sophisticated and powerful offensive cyber capabilities and platforms imaginable, in order to monitor, degrade and defeat the enemies of Western Civilization
—
If this sounds like what you’re after, reach out. Careers@IRISC2[.]com
Today’s models are still not very capable of taking the log from an incidental memory corruption crash and creatively turning it into an RCE primitive the way that the best human exploit developers are able to
I anticipate that we are probably 1 or 2 updates away from that
We built a custom HEIC compiler that to solved for cell characterization, logic synthesis, register allocation, liveness, placement, routing, crossing, carry propagation, bank assignment, motion-vector reachability, and physical verification, in order to generate an HEIC image which spawns an artificial processor (or weird machine) within Apple’s decoder, such that the image displays file’s own SHA-256 hash value
irisc2.com/blog/heic-hashqui…
In the West, offensive cyber has been heavily pervaded by an incessantly feminine, listless, hollow, flabby energy
Remember: The only purpose in any of this is to deliver as many bad days as possible to communists, terrorists and other scum around the world
Steal their secrets
The crypto industry is run by a bunch of completely negligently incompetent jackasses
Outside of places like Bangladesh, this kind of thing basically never happens in the traditional banking world
We owe you an apology.
On October 20, we detected unauthorized access to our official website. After verifying API activity with Shopify, we confirmed on October 23 that a third party obtained customer shipping information. You trusted us with those details, and we're sorry we didn't keep them safe.
Exposed: names, contact details, shipping addresses, and order details (items and prices).
Not exposed: payment card or bank details, recovery phrases, private keys, or wallet passwords.
We've blocked access, fixed the vulnerability, opened an investigation, and are emailing affected customers.
Scammers may pose as Keystone by phone, text, email, or mail, offering refunds, replacement devices, or "fixes" for your order or address. None of it is from us.
NEVER share your recovery phrase or private keys, and NEVER enter your recovery phrase into a device you didn't order. We will never ask for them. Don't click links in unexpected messages. Type keyst.one yourself.
A detailed report is coming soon.
Until then, trust only our official channels. If anything feels off, email [email protected]. We'd rather hear from you than have you take a chance.
Again, we're truly sorry to everyone affected.
We have already achieved this internally.
Palmer Luckey unveils start-up to breed ‘genetically enhanced’ dogs for military ft.trib.al/x5vest0
If we lived in a world where the AI models never got any better than Claude 4.5 Opus, then I think Rust would have some real usefulness for people who are aiming to reduce their cloud compute bills and increase performance by refactoring their backend Python/Node microservices into Rust.
Most of the benefit would come from the Rayon crate’s ability to deliver relatively effortless concurrency.
But the models have gotten a lot better, so I don’t see any reason why you wouldn’t take the time to just build these sort of services in C++, assuming that you have even the most basic familiarity with how to ensure that this C++ is written properly (given that the latest models still tend to write less than totally professional C++ code)
The PHP/Python/Javascript problem explained for normies: These are scripting languages. Scripting languages were intended for writing scripts, or very lightweight software that resembles scripts—like data science (remember R?), JS landing pages, etc. They were not intended to be used as the backbone of mission-critical software.
They work using these things called interpreters (or JIT compilers), which are other software that converts the scripts, ultimately, into machine code through one or more layers of abstraction.
Those layers of abstraction involve complicated details that you don’t want to know, and, in fact, don’t need to know, if you use those languages for their intended purpose(s).
However, if you choose to use these scripting languages for purposes that go beyond writing scripts, you are subjecting yourself to the distinct possibility that the complicated details of what exists—or doesn’t exist—under the hood, might end up biting you very badly from a functionality, reliability or security standpoint.
You might wonder why the hell the a firewall would be programmed in PHP
The answer, as always:
There are an increasing number of YouTubers who I can no longer listen to because they use AI to write their scripts.
I used to really enjoy their extemporaneous commentary, but now their videos are infected with the never ending verbosity and cringeworthy AI-isms
You really want to vibecode your own Adobe Acrobat?
CVE-2026-81983: Integer overflow leads to an out-of-bounds write in Adobe Acrobat
Read on dbugs: dbu.gs/news/cve-2026-81983-i…
Remedio researchers discovered CVE-2026-81983 (dbu.gs/vulnerability/CVE-202…) in Adobe Acrobat's image-processing pipeline. The vulnerability is triggered by opening a PDF containing a specially crafted 16-bit image and can cause an out-of-bounds write in "Acrobat.dll".
The flaw lies in a function that normalizes 16-bit image samples before compositing. The byte-swapping loop uses the product of the image width and the number of components as its iteration count, without checking it against the buffer size. Meanwhile, the buffer-size check calculates the required data length as "Width × components × 2", using the same 32-bit arithmetic.
A CMYK image with a width of "0x20000000" is sufficient to trigger the vulnerability. The product "4 × 0x20000000" yields "0x80000000". Multiplying this by two during the size check causes the 32-bit result to wrap to zero, allowing an image data stream containing just 8 bytes to pass validation.
The byte-swapping loop then uses the original iteration count of "0x80000000", advancing through memory two bytes at a time. The minimized trigger is a 745-byte PDF containing a single image row. The loop reads and writes beyond a 16-byte buffer, with the observed access violation occurring approximately 144 KB beyond the buffer's start.
The vulnerable code is part of the 16-bit sample normalization routine, which swaps the bytes of each value directly in the source buffer. Whether this branch executes depends in part on the "keepEndian" flag. The minimal trigger uses an image XObject with "/BitsPerComponent 16", "/ColorSpace /DeviceCMYK", a height of 1, and a width of "0x20000000".
Adobe fixed the vulnerability by introducing a 64-bit range check and rejecting sample counts greater than "INT_MAX". The fix was published in security bulletin APSB26-141 on September 8, 2026. The fixed versions are Acrobat / Acrobat Reader Continuous "26.002.21901" and Acrobat 2024 Classic "24.001.30429".
Article: remedio.io/blog/cve-2026-819…
CVE-2026-81983 — PT-2026-88482: dbu.gs/vulnerability/PT-2026…
