CloudSEK

The BigBear 2.0 phishing service compromised Microsoft 365 accounts at two hundred and fifty-eight organizations and captured more than five thousand credential records across more than 40 countries.

CloudSEK found four hundred and seventy-four completed MFA bypasses and over four thousand one hundred stolen session cookies in the services control panel.

BigBear sits between a victim and Microsoft's real login page.

It captures the authenticated session after MFA, then replays it through a residential proxy matched to the victim's location.

Police allege the campaign potentially compromised more than 1,000 organizations, stole more than a half a million credentials, and exfiltrated at least 300 gigabits of data.

Cybersecurity firm CloudSEK put the total credential exposure at more than 2,500 organizations.

In May, TeamPCP open sourced its Shaihulud worm framework on GitHub.

At the time, it looked like an attempt to muddy attribution by putting the tooling in everyone's hands.

CISA says exploitation can allow unauthorized access, modification, or deletion of critical data.

CloudSEK previously observed attacks targeting the vulnerability in its honeypot environment.

Exposed Oracle components could provide attackers access without valid credentials.

Both CISA and CloudSEK report active exploitation.

Taiwanese prosecutors have charged nine people over the alleged illegal export of high-end AI servers to mainland China, including individuals linked to NVIDIA and Supermicro.

Prosecutors say the case involves servers using B300 graphics processing units, which the report says are banned from sale to China.

Sometimes raising money too quickly can be... [upbeat music]

Hi, this is Siddhartha Ahluwalia, your host at Neon Show and managing partner at Neon Fund, a fund that has invested in some of the best enterprise AI companies between US-India corridor, like Atomicwork, SpotDraft, CloudSEK, and many others.

Today I have with me Krishna Mehra.

Krishna, welcome to the Neon Show.

Well, we've learned that there's sort of a difference of opinion.

So the, the first article came out, was from, uh, CloudSEK and Hudson Rock.

Now, Hudson Rock had gotten access to a eye-wateringly large 195 terabyte file that apparently contained all these credentials that had been snapped up.

And this comes back to the, the March sort of era attacks around LightLLM, Trivy, et cetera, and but there, the attribution from CloudSEK and Hudson Rock was directly back to LightLLM as being the attack that netted all of these credentials.

The second report that's come out, though, is actually from, um, SOC Radar, who, who said, "Well, look, the, we agree that that's the credentials that have been, uh, taken in these attacks, that it all happened around that timeframe of Team PCP and the many supply chain hacks that were happening almost daily." But they checked the timestamps and said, "Look, in this data set, there is actually records of when the credential was first seen, when it was last seen, and for the vast majority of these, about 95% of the credentials, they were all first seen before the LightLLM attack." And so it appears to be actually Trivy was the, the source for these, which to me makes a lot more sense, right? Y- y- an, an exploit of Trivy, whether it is happening on a developer's laptop in a CI/CD pipeline, it's a more mature product, and it's gonna happen in places that have cloud credentials, IAM credentials, all sorts of things.

LightLLM never really made that much sense to me.

Microsoft, Amazon, Cisco, Samsung, and Salesforce are only a handful," he writes, "of the entities whose access secrets were exposed.

The revelation was posted on Tuesday and Wednesday," that's la- of last week, "by security firms CloudSEK," you know, E-S-E-K, "and Hudson Rock.

CloudSEK said it found keys, repository tokens, SSH keys, Kubernetes secrets, package publishing credentials, environment variables, and AI provider keys that could allow attackers to gain access to more than twenty-five hundred organizations, and forty minutes is all it took.

The credentials were extracted during a forty-minute window in March, while the victims used un- o- obviously unknowingly, compromised versions of LiteLLM, which had been downloaded from the package's official location in the Python Package Index repository." You know, uh, PyPI.

Hudson Rock said it made the discovery after analyzing a, woo, one hundred and ninety-five terabyte file that it had obtained.

I'll clarify that in a second.

Yeah.

Um, in many cases, the researchers at CloudSEK and Hudson Rock had trouble identifying, which is a problem, the organizations, uh, the credentials belonged to.