Yahoo?
People still have yahoo emails?
<desperately trying to remember if I had one....>
The US Cybersecurity and Infrastructure Security Agency (CISA) left open a GitHub repository named “Private-CISA” containing plain-text passwords, private keys, tokens, and secrets – with obvious file names like “external-secret-repo-creds.yaml” and “AWS-Workspace-Firefox-Passwords.csv” – for six months. GitGuardian researcher …
Yeah, unfortunately, they do - one's a website client of mine and I've warned him several times about their skanky service and the need to whitelist accounts of people he knows - many of my emails to him either disappear or end up in his spam folder. But, despite my warnings, does he ever do anything about it? Of course not.
Man the nostalgia in that question.
Everyone with an email address back in the day probably had a Yahoo email address at some point if they're over a certain age. They were pretty much the only free mail provider with a decent webmail UI for quite a while. That changed with hotmail.com though.
It's insane how much grip Yahoo had that they then fumbled.
Yep. And, I can't remember what movie it was, was a comedy, while on a golf course, time travel related, someone said something along the lines of "Remember the name Yahoo and reserve it". Ignoring the fact if the name was reserved, they'd have probably gone with something else.
To be fair, I still have a yahoo email address, and it works just fine; it's probably one of the few free email providers of the time that is still going.
Given that they have stood the test of time, are you suggesting I switch to another provider? Yes I have a Google email address, but the interface to Google mail is god-awful, and they rate-limit POP3 and IMAP access.
As with all things, you get what you pay for, and for zero pounds and zero pence, their offering is both long-lived and pretty reliable. I think maybe snootiness is playing a part here, I wonder how many email providers of today will still be about in 20 years' time?
Me and a colleague actually defined professional stupidity mathematically a couple of decades ago for the laughs...it was an equation that worked quite well when determining if a person we hadn't worked with before was technically incompetent. I wish I still had it...alas it became lost to time.
We tested it across all known members of staff at the company we worked at and graphed it...it was pretty bang on.
We were given a written warning for it because "calculating someones level of competence could be deemed to be offensive"...by that, what my line manager meant was that he was offended that he came out as below average competence for the company...actually the lowest by quite a margin.
The variables we took into account were length of service in their current role, total time spent at the company, average number of cock ups per month, number of times they had been promoted, total time logged in the timesheets and a few others.
Time served at a given company and the number of hours officially logged in the timesheets were the biggest determining factor a lot of the time...and you could actually graph timesheet hours per month against a time series and map the competence decline...also the longer you've served at a given company, the nearer to 0 you trend on the competence scale...we forecasted that it would only have taken an additional 4 years at the company for our line manager to become thick as mince and functionally useless.
Us: Guys, we've made a formula to work out how useless or competent someone is.
Office: lol
Manager: Hah, alright then, lets see the results...who is the dumbest person here based on your maths?
Us: Haha ok then, it was you by about 32%...see look at these charts.
Office: ROFL! *literal tears of laughter all around*
Manager: *shock* You two, my office, now!
Man, he got shit for a long time after that.
Manager: I reckon we should approach this like XYZ.
Engineer: Sounds good, but mathematically speaking...
Had it been a honeypot, the researcher who found it would have been made aware the first time he contacted the CISA people, and nobody besides the CISA and researcher would have been the wiser.
OR, it actually was a honeypot operated by a team that was fired.
If this was the case, it's still awful PR for CISA and an eventual signal to hackers that the current team is dysfunctional and an open invitation to hackers.
The primary cuts, structural changes, and key leadership shifts impacting CISA include:
1. Mass Personnel & Contract Cuts:
- Red Team Terminations:
DOGE eliminated CISA’s entire core "red team" (the specialized ethical hackers who simulate cyberattacks to find network vulnerabilities) along with their support roles.
A follow-up cut eliminated a second red team doing critical work.
In total, over 100 highly skilled penetration testers and operators had their contracts abruptly ended.
- Probationary Employee Layoffs: In mid-February 2025 (during an event federal workers dubbed the "Saint Valentine's Day Massacre"), DOGE directed the Office of Personnel Management (OPM) to slash probationary staff. This resulted in the firing of roughly 130 probationary CISA workers.
-Election Security & Disinformation Experts: The cuts heavily targeted CISA's election security advisers (the non-partisan liaison experts coordinating security with state and local governments). Concurrently, many staff members assigned to CISA’s foreign influence and disinformation teams were placed on administrative leave.
2. Major Defunding & Partner Dissolutions:
- Termination of the $10M CIS Partnership: CISA cancelled its multi-million dollar cooperative agreement with the Center for Internet Security (CIS). This effectively shut down federal funding for two major cyber-threat info-sharing hubs: the Multi-State Information Sharing & Analysis Center (MS-ISAC) and the Election Infrastructure Information Sharing & Analysis Center (EI-ISAC).
- Disbanding of the Cyber Safety Review Board: The administration disbanded the Cyber Safety Review Board, pausing deep-dive federal post-mortem investigations into major corporate and governmental hacks.
3. Leadership Shakes-up:
The Exit of Jen Easterly: Longtime CISA Director Jen Easterly officially stepped down on January 20, 2025.
Nomination of Sean Plankey: To fill the vacancy, President Trump nominated Sean Plankey to become the new Director of CISA. Plankey is a Coast Guard veteran who previously served as the Navy's Deputy Chief Information Officer (CIO) for Naval Intelligence and worked on cyber policy during the first Trump administration
Open repo > Settings > scroll down :
a) Change Visibility > Private
OR
b) Delete this Repository > I want to delete this repository
Took me 1 minute to figure out without asking a chatbot or googling.
NOTE: I use Gitlab, my Github repo is only for my Kitty config files.
A CISA spokesperson told The Register that it was aware of the report and is investigating. "Currently, there is no indication that any sensitive data was compromised as a result of this incident.”
In other words: "I surveyed my cat, Mittens, who did not affirm she misused any of the leaked credentials. So, currently, there is no indication that any sensitive data was compromised as a result of this incident.”
So for 6 months their admin passwords were online but 'there is no indication that any sensitive data was compromised'
a) Your admin passwords are sensitive data.. If you don't believe this you have no business running an IT system.
b) The bad guys have wiped the logs, you buffoons. Your *entire system* should be considered compromised at this point. God knows how you roll back 6 months, assuming the backups aren't compromised too..
and c) You're a fucking cyber security agency. If *you* can't get this right then we're fucked.
Unless it is indeed just a honeypot, but really I don't get those vibes from that response.
No, it really fucking isn't.
This is a complete shit show and the fact they took action after the press got notified does not make this "impressive work", it makes it a desperate attempt to shut the stable door months too late.
Sounds a lot like someone was told to make all this information available to either the DOGE kids or their 'replacement' when they were getting 'rightsized' out of the organisation.
A nice bit of malicious compliance. Technically, the information is available to their replacement. It's just also available to the rest of the world. Unless they were told to make it secure, then it's very much Someone Else's Problem.
Another possibility is that someone was asked for the credentials, provided them somehow, and the recipient is the one who posted them to a repo to store them. Even that wouldn't be the most relieving because anyone with too many credentials to store should have a more organized method for doing so securely. Unfortunately, credential management is a thing where many organizations don't have great answers and looking at what they do just shows you a horror which will be very painful to clean up.
credential management is a thing where many organizations don't have great answers
The answer is usually an Excel spreadsheet saved to SharePoint... Occasionally it might even be password protected. With the password in a Word document in the same folder called password.docx.
Am I not understanding something essential because taking fork count as any kind of indication about anything seems wrong. Unless someone specifically wanted to signal back to the owner that "I have your files".
Also, even though this is a major bureaucratic entity, a day's response time can't possibly be considered "impressive"? In this line of work, at least.
Well, the thing is, if you run a honeypot, you don't want the bad guys to figure out that you're running a honeypot, or even that you were running a honeypot until yesterday (otherwise, they'll be more suspicious of future honeypots).
So, in this case, an amazingly competent CISA would look exactly the same as an amazingly incompetent CISA. Each of us can pick their favorite version, happily call the other camp idiots, based on the same amount of evidence.