ALPHA-RTD

C# , C++ , Python , JS (Looking for work)
Seizure Haver ( not the flashing kind )

[ALPHA-RTD @dbCo0ps]

to the person spreading rumors about me , i think it's funny you RT someone who stalked my partner for a year straight , but yeah
you do you

you're such a GOOD PERSON , siding with that fucking piece of shit , lmao

[ALPHA-RTD @dbCo0ps]

i mean i know who did it cause it was stupidly easy to figure out , thanks for coming to me ted talk

go read an opsec guide lmao

[ALPHA-RTD @dbCo0ps]

#MyXAnniversary

i wanted to blow my grey matter on a wall and was alone , and made this series of accounts ( DB has been my alias long term )

Now i'm right back where i started, Nobody around again
thx person spreading rumors, whoever you are, you're garbage juice, fuck yall

[ALPHA-RTD @dbCo0ps]

@BrainAblaze they should at least teach people to not stick spoons and other metal / hard objects in a persons mouth and resting position shit , but nobody cares about epileptics

[scar :3 @scarlettactual]

update from the client:

she said yes! congrats to the happy couple🥳

(censored because he got her name inlaid in 24k gold on the slide)

[The Lunduke Journal @LundukeJournal]

Yet another massive attack on Rust Crates (code library collections), compromising potentially millions of Rust programmers.

Every Rust programmer who compiled *any* project which referenced one of the compromised Crates (including the popular "arrayref" crate, which has been downloaded over 244 million times), unknowingly also downloaded the "proc-macro1" Crate... which contained the malicious code.

This is not the first time a malicious Rust crate has been discovered. In fact, it's a regular occurrence (see "onering" Crate from just two months ago).

As these repeated malicious code events suggest, the design of the Rust Crate system is inherently insecure.

In fact, based on the frequency and severity of malicious code being added to the Rust ecosystem, there's a strong case to be made that Rust is the least secure programming language ecosystem today.

https://t.co/OjDxdaWxNZ

[Boschko @olivier_boschko]

Now that Unitree has IPO'd, I'll drop what will likely be my last blog sometime next week. I'm not quite done writing just yet 🙃 It's ~3 months (~200h) of research condensed into ~70 minutes. Exploit is wormable, so if one G1 gets popped, it RCEs all other G1s in proximity

[International Cyber Digest @IntCyberDigest]

New subdomain lookup tool just dropped.

https://t.co/8lD04pCf4i

[Winston Ighodaro @Officialwhyte22]

We had a Windows laptop that looked completely normal at first.

Defender was quiet, there was nothing suspicious sitting in Downloads, and Task Manager did not show anything that immediately looked wrong.

But one thing kept happening.

Any time the user logged in, PowerShell would start in the background.

That was what made me check the persistence locations.

I went through the user’s Run key in the registry:

HKCU\Software\Microsoft\Windows\CurrentVersion\Run

and found an entry called:

Windows Security Health

The name looked normal enough, but the command behind it was not.

It was launching PowerShell with the window hidden and running this script:

C:\Users\ola\AppData\Roaming\Microsoft\Windows\cache.ps1

At that point, I checked the file timestamps and saw that the script had been created the previous afternoon around 4:22 PM.

Then I went into the Sysmon logs.

Event ID 13 showed the registry Run key being modified around the same time the script was created.

Event ID 1 also showed PowerShell starting again the next morning after the user logged in.

So now the timeline was starting to make sense.

The user logs in.

Windows processes the Run key.

PowerShell starts quietly in the background.

The script runs.

I checked the network connections from the PowerShell process and found an active HTTPS connection to an external address on port 443.

That was enough for us to isolate the laptop and start preserving the evidence before removing anything.

When we spoke to the user later, he remembered opening what he thought was a company document the previous day.

He said nothing happened when he opened it, so he assumed the file was bad and forgot about it.

Meanwhile, the persistence had already been created.

What made this case interesting for me was how normal everything looked.

There was no malware.exe.

No strange folder sitting on the desktop.

The attacker used PowerShell, the Windows registry, AppData and a name that looked like it belonged to Windows Security.

If you were checking the machine quickly, you could easily pass over it.

Sometimes malware does not hide by looking strange.

It hides by looking like something you have seen a hundred times before.

[ALPHA-RTD @dbCo0ps]

Like laughing at a person without legs, hilarious no matter what the context is

If it's someone you disagree with , it's all good right?

Like nah that's some scum shit right there.

Thanks for spreading rumors about me ya fuckin weirdo

[ALPHA-RTD @dbCo0ps]

https://t.co/vH0T4Qh6cm

HAHAHAHAHA HE LOST HIS LEGS AND CANT WALK , GET IT GUYS????
ITS FUNNY CAUSE HE CAN BARELY WALK

ISNT THAT SO FUNNY ?

HAHA THIS PERSON IS DISABLED HAHA

This sets a fucking stupidly dangerous precedent but, yeah keep being ablest garbage humans

[ALPHA-RTD @dbCo0ps]

It's so fun and funny to pick out the flaws in others.

[Fox @BowTiedFox]

everything is hyper engineered to make you addicted

[ALPHA-RTD @dbCo0ps]

tldr google gives up ur data to cops

[International Cyber Digest @IntCyberDigest]

‼️ BREAKING: The Netherlands Forensic Institute has found a way to crack Google Pixel phones, though it did not say which OS the phone was running. There is a high chance they were using an OS like GrapheneOS, since all three suspects were using Google Pixel phones. Or perhaps they are just fans of Google products.

They have already cracked one of the suspects' phones — that of Swedish national Veronica K., a suspect in a triple murder — prosecutors told the high-security court at Schiphol today.

The phone held images of weapons and stacks of cash, plus chats investigators can now read. The Forensic Institute expects to crack the two co-defendants' Pixels too.

[ALPHA-RTD @dbCo0ps]

GET YOUR OWN GUNDOG TODAY

[Lukasz Olejnik @lukOlejnik]

Remote code vulnerability found in Unitree robots and the scary part is that the exploit is wormable. That means one compromised robot could infect other vulnerable robots nearby, turning a single breach into a wide compromise. Could attackers then take control of entire fleets of humanoid robots? https://t.co/kyKMKKG9lE

[ALPHA-RTD @dbCo0ps]

bet money C is laughing at me and my epilepsy flare up and shit , they caused this shit why the fuck did they do it?

i dont get it, why do people betray others silently?

it's insanely fucked up and weird

[ALPHA-RTD @dbCo0ps]

You're fucking crazier than I am , and that's fucking sayin something, get your shit together.

[ALPHA-RTD @dbCo0ps]

Vagueposting about someone who fucked me over lost me a friendship. It's like someone knows how exactly to destroy someone in my mental state.

It's hilarious how y'all fell for that shit and really really sad.

[ALPHA-RTD @dbCo0ps]

I vague post about someone but you're ego is so big you took it on yourself

What a great human , why do you buy into this shit? cause these people just agree with everything you say?

There is manipulative weird shit going on here with Ian and Conde.

[ALPHA-RTD @dbCo0ps]

to the person spreading rumors about me , i think it's funny you RT someone who stalked my partner for a year straight , but yeah
you do you

you're such a GOOD PERSON , siding with that fucking piece of shit , lmao

[ALPHA-RTD @dbCo0ps]

you're best friends with a stalker, while calling me a stalker, you fuckin weirdo piece of shit

[ALPHA-RTD @dbCo0ps]

Vagueposting about someone who fucked me over lost me a friendship. It's like someone knows how exactly to destroy someone in my mental state.

It's hilarious how y'all fell for that shit and really really sad.