optional

The proud owner of two brain cells. HTB with @barctf | OSCP, CRT, CRTL

[optional @optionalctf]

Introducing C2structor, a deployment tool to automate red team infrastructure within AWS.

Utilising Terraform and Ansible to allow for seamless customisation to each individual's use-case.

Currently supports C2 deployment, redirectors and phishing inf.

https://t.co/TpILGtNC8w

[optional @optionalctf]

A 5 submission limit is becoming ridiculous when it's taking 4-8 weeks to progress the report and free up a space.

Wouldn't be so bad if the criteria were public knowledge on how to increase it

[optional @optionalctf]

Can we all agree that Delay Repay is an incredible scam? Twice declined because they require a scan of the ticket. Which is fine but the digital ticket is already attached.

@GWRHelp do better, or perhaps actually run your services on time so this entire system isn't needed

[kepano @kepano]

This is Knap. It's a new language I created that turns data into Markdown. The syntax should feel familiar and comes with wonderfully pleasant features to modify and format plain text.

Knap is open source. Over a million people already use Knap directly or indirectly because it started as the templating language I made for Obsidian Web Clipper. Now any tool can use it.

You can add Knap to your app or use it via CLI. Create a batch of Markdown files from JSON or CSV, or pipe Defuddle directly into Knap to generate Markdown from HTML/URLs.

The Knap site is color-coded to help beginners understand the relationship between variables (blue), filters (orange), and logic (green). I've tried to document it as comprehensively as I can.

Try the Knap Playground so you can see how fun the syntax is to use!

Knap is pronounced /knæp/ (with a hard k). It's named after knapping (with a silent k): the process of shaping stones to form arrowheads, scrapers, and other tools.

Enjoy!

[optional @optionalctf]

Not in much of a rush to get hold of Astra but a couple of resets would be amazing

[Tibo @thsottiaux]

We will give one banked reset for every day you don't have access to Astra on your paid ChatGPT plan, starting today. Team is moving mountains to give access as fast as we can.

First one will land in ~ 3 hours. There is still time to create your account if you don't have one.

[optional @optionalctf]

This might be a reach, but does anyone have a contact at Bugcrowd they can put me in touch with?

[optional @optionalctf]

I miss the days when bug submission to response was <48 hours

Can't wait for one of my five submission spots to free up to submit these crits, only for them to be marked as dupe in a few weeks once triage finally gets around to them

[Tibo @thsottiaux]

What I wanted to say yesterday is that we hit 25M active users and to celebrate we have now reset usage for all paid subscriptions for ChatGPT Work and Codex.

See you soon for more news from The Reset Company.

[optional @optionalctf]

First time using Bugcrowd, I get why they have a 5 submission limit on managed programs, but when you've got a bunch of P2s sitting in draft because of it, it absolutely sucks.

Guess it's my fault for not giving the platform a proper chance in the past

[Tibo @thsottiaux]

We unfortunately have decided that we cannot continue providing access to our models through Cursor and are ending our partnership. It boils down to trust and we’ve asked that this takes effect on November 12 to give you some time to plan.

Many have used the GPT models through Cursor and here are options we know should work in the future:

- We will continue to allow using your own OpenAI API key and similarly will continue to provide access through our IDE extensions for Cursor.
- We will keep working with the broadest range of tools and harnesses, some of which are OSS, but also many many closed-source ones.

We are as committed as ever to continue supporting developers and the flourishing ecosystem of tools, harnesses and products. We will also continue to invest in our own open-source initiatives and believe in broad optionality for developers.

You can read more about our decision in the blog:
https://t.co/Oj76Bkc2KX

[Dominic Chell 👻 @domchell]

I've been fairly quiet about recent events for good reasons, but this popped up on my radar - https://t.co/PEf4MGCIzr

I don't have much to say except some companies will forever lack class. For anyone looking for a new pentest, red team or c2 product vendor, there are many great ones out there and do your homework - the ones I am personally familiar with and would wholeheartedly recommend are @AmberWolfSec, @remotethreat, @SpecterOps, @OutflankNL and @TrustedSec ❤️

[Mark Zuckerberg @finkd]

Today we're also opening the weights for Muse Glimmer, a great 30B parameter dense model that can run locally. Soon we'll also release the weights for Muse Spark 1.2, our latest foundation model. Meta is a strong supporter of open source and I'm proud of these releases. Congrats to @alexandr_wang and the MSL team for all your great work on these models.

[optional @optionalctf]

Big shoutout to Coinbase and other companies taking this approach, ensuring cyber security professionals have plenty of work for the foreseeable

[Brian Armstrong @brian_armstrong]

This is an email I sent earlier today to all employees at Coinbase:

Team,

Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future.

Why now
Two forces are converging at the same time. We need to be front footed to respond to both.

First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth.

Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day.

All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core.

What this means
To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice?

- Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles.

- No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams.

- AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role.

In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs.

To those who are affected
I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done.

All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information.

To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements.

Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters.

How we move forward
To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together:

Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it.

The Coinbase that emerges from this will be more capable than ever to achieve our mission.

Brian

[Ben Sadeghipour @NahamSec]

Unfortunately most of the execs at these bug bounty platform fail to understand one thing:

Your platform isn't your product... your hackers are. 🤷🏽‍♂️

[Patrik Grobshäuser @ITSecurityguard]

built a web interface for https://t.co/6bzg5bU4jL so you can access your vault from any browser using cloudflare tunnels + your own hostname.

No more being stuck with notes on one machine, no installing clients on work computers you don't control 👀

👇
https://t.co/D1eGoNZwEm

[klez @KlezVirus]

[RELEASE] As promised, I’m releasing the first blog post in a series. It covers the gaps still present in current stack-based telemetry and how Moonwalking can be extended to evade detection logic and reach “on-exec” memory encryption.
Enjoy ;)
https://t.co/4Yf28y7cT4

[Bobby Cooke @0xBoku]

Venom C2 tool drop! 🐍

During a recent red team engagement we needed a simple python agent that needs no dependencies to setup persistence on some exotic boxes we landed on.

Some had EDR so we didn't want anything off-the-shelf.
The server, agent, and client were made mid-engagement and kept our foothold for weeks. I have no use for this anymore, so thought i'd share it instead of letting it evaporate into the /dev/null.

Link to boku7/venom GitHub repo : https://t.co/YKY3txKHA9

[optional @optionalctf]

Labour's 1984 shit show is already showing cracks and backfiring.

Can't wait to see the shit show Digital ID gets compromised because they rushed to implement something no one wants...

[vx-underground @vxunderground]

Discord has begun sending e-mails notifications about a cybersecurity incident which occurred September 20th, 2025.

It appears people who submitted support tickets are the ones primarily impacted.

Literally peoples entire identity stolen from this shit

[Nathan McNulty @NathanMcNulty]

It gets better ;)

I totally forgot about this little persistence method, lol

[kreep @kreepsec]

AWS quietly updated T&Cs to ban “Fireprox”style use of API Gateway closing a handy pentest trick. @ZephrFish and @turvsec already rolled alternatives such as Omniprox and Flareprox. Banning tools only hampers legit testers, attackers will proxy anyway.