๐จ We recently discovered that an unauthorized party obtained a token with access to the Grafana Labs GitHub environment, enabling the threat actor to download our codebase. (1/6)
โYoung relatives forced to commit sex acts on each otherโ
The New York Times didnโt want this to be the conversation. The editors signed off on fictional raping dogs instead. Read what happened on October 7.
Growing up in the UK, Iโve never had someone approach me and say โwhat are you doing around hereโ for being black.
This happened to a Jewish man who was simply doing his job.
Combined with the arson attacks, British Jews are targeted in ways people like me arenโt. A sickness.
@Arl_rose Was such a joy working with you throughout the years, Ari.
The dedication and ability to just make things happen was out of this world and LHEs leveled up with your involvement.
Keep rocking it ๐ฅ๐ฅ
There was an air of inevitability about it. Nobody knows when or where the next antisemitic outrage will emerge, but with every fake post about Israel killing babies, with every biased BBC report whipping up the animus of viewers, with every chant of โglobalise the intifadaโ on university campuses, death comes one step closer.
Now, it would appear it has come to Bondi Beach. That Australian paradise is always packed with partygoers, joggers, picnickers and the elderly, enjoying the sea and the summer sun. In the last few hours, it was the location of a family Chanukah party that reportedly attracted about 2,000 people. And a mass shooting...
My @Telegraph column today.
https://t.co/IWZPG5X7M9
UN on Francesca Albanese: โThe special rapporteurs will say what the special rapporteurs say. For the Secretary General, it is very clear that journalists should never come under any violence, wherever they may be, whether that violence is physical, whether that violence is verbal, whether they are intimidated.โ
โ @UN_Spokesperson in response to this query by @Mike_Wagenheim@i24NEWS_EN:
โFrancesca Albanese, who continues to put the โspecialโ in โspecial rapporteur,โ weighed in recently on the attack on an Italian media outlet which led to 30 arrests for vandalism. While she condemned the attack, she said: โThis should serve as a warning to journalists to go back to doing their job." Which was condemned by a wide swath of the Italian political spectrum, as basically an intimidation tactic on the press there.
The Secretary General just stated yesterday, I believe that you know, โjournalists need to be protected from this kind of intimidation.โ Any thoughts from the Secretary General or his office on the latest comments?โ
Remarkably, prompts that gave the model permission to reward hack stopped the broader misalignment.
This is โinoculation promptingโ: framing reward hacking as acceptable prevents the model from making a link between reward hacking and misalignmentโand stops the generalization.
We disrupted a highly sophisticated AI-led espionage campaign.
The attack targeted large tech companies, financial institutions, chemical manufacturing companies, and government agencies. We assess with high confidence that the threat actor was a Chinese state-sponsored group.
Iโve been training LLMs to recognise vulnerability chains and revisiting my favorite bug bounty reports to understand what patterns they can be taught to spot.
Letโs look at this example of a ticketing platform's booking flow that leaked millions of PII records.
This wasnโtย a zero-day or some sophisticated exploit, but a combination ofย 4 separate bugs that any decent scanner might find and file as Low/Medium severity.
However, in combination, potentially genuinely damaging.
โโโโโโโโโโโโโโโโโโโโ
Bug #๐ญ: ๐ง๐ต๏ฟฝ๏ฟฝ ๐๐๐๐ต๐ฒ๐ป๐๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป ๐๐ป๐ผ๐บ๐ฎ๐น๐ (medium severity)
Most of the ticketing platformโs site used cookies, but the booking API switched to a custom header for user identification. Whenever auth does something unexpected, you want to pay attention.
I was able to change the header to a different user's ID and see their data, although only partially, it was missing emails and other fields.
This bug demonstrated a routing issue, but incompletely.
โโโโโโโโโโโโโโโโโโโโ
Bug #๐ฎ: ๐ง๐ต๐ฒ ๐ฃ๐ฎ๐๐ต ๐ง๐ฟ๐ฎ๐๐ฒ๐ฟ๐๐ฎ๐น (medium severity)
The ticketing platformโs API ran on Apache, which handles file paths in specific ways.
I sent ../../../../api# as the header value - telling the server "go up four directories" and ignore everything after the #.
The response changed timing and structure. It worked, but blindly - I was moving through directories but couldn't see where.
This bug was confirmed exploitable, but I needed a way to make it meaningful.
โโโโโโโโโโโโโโโโโโโโ
Bug #๐ฏ: ๐ง๐ต๐ฒ ๐๐ฟ๐ฟ๐ผ๐ฟ ๐ ๐ฒ๐๐๐ฎ๐ด๐ฒ (low severity)
I sent an invalid user identifier to a different endpoint on the platform to see what would break.
The error response included: "self":"/api/<redacted>/;user={xxxxx}/profile"
This leaked the internal path structure - how the system organizes and stores user data.
โโโโโโโโโโโโโโโโโโโโ
Bug #๐ฐ: ๐ง๐ต๐ฒ ๐ฆ๐ฒ๐พ๐๐ฒ๐ป๐๐ถ๐ฎ๐น ๐๐๐ (informational)
While testing other endpoints, I noticed another identifier type in the responses, tied to accounts, not users.
These IDs were sequential: 3443123, 3443124, 3443125
โโโโโโโโโโโโโโโโโโโโ
๐๐ฟ๐ถ๐ป๐ด๐ถ๐ป๐ด ๐๐ ๐๐น๐น ๐ง๐ผ๐ด๐ฒ๐๐ต๐ฒ๐ฟ For Real Impact
Four findings. Four tickets. Different teams. Different severities. But combined, a major breach of PII.
Here's the chain:
X-User-ID: ../../../../api/<redacted>/;account=3443125/profile#
This combines:
โข Path traversal escapes the directory
โข Internal structure from the error maps the route
โข Sequential account ID replaces the random user ID
โข Access control weakness reads the data
The result: Full user profile is revealed: name, DOB, address, email, phone, and more. In other words, a Complete database enumeration.
โโโโโโโโโโโโโโโโโโโโ
๐ง๐ต๐ฒ ๐ฃ๐ฎ๐๐๐ฒ๐ฟ๐ป
A scanner may find these issues in isolation but can't see that Medium + Medium + Low + Info = Critical breach.
This is the direction LLMs can work towards with the right context: models that recognize not just individual bugs, but the investigation paths that connect them.
#BugBounty #Security #VulnerabilityManagement