Chat, all hell has broken loose in the Linux community.
Linux nerds are discussing how they'd implement age verification at the OS level (if need be to comply with laws).
Linux nerds are having a psychiatric meltdown. The nerds are revolting.
Linux nerds are discussing how they'd implement age verification at the OS level (if need be to comply with laws).
Linux nerds are having a psychiatric meltdown. The nerds are revolting.
π87π€£58π26π’20π€―6β€5π€3π2π₯°1
This media is not supported in your browser
VIEW IN TELEGRAM
π₯°76π€£70π6β€4π±4π₯1
vx-underground
The FBI (and apparently every other government agency on planet) has seized LeakBase, the long standing competitor to Breached, with the difference being LeakBase was more tailored to Eastern Europeans. Hot take: Operation Leak is an unoriginal and lazy name
Also, I think Kash Patel laid off the FBI Special Graphics Unit, because I think that background is AI generated
π€£86π₯°13π9π±4β€3π2
> black mass vol 4
> call for papers
> need to do something cool
> something unique
> need ideas
> "hmm... malware only using rpcs?"
> nah
> "hmm.. polymorphic mutation engine?"
> nah
> "self-rewriting polymorphic mutation engine?"
> nah
> "position independent self-rewriting polymorphic mutation engine?"
> nah
> "position independent self-rewriting polymorphic mutation engine with embedded obfuscated powershell?"
> hmmm... maybe
> "position independent self-rewriting polymorphic mutation engine abusing uefi nvram variables in motherboard flash memory with sliding key encrypted embedded obfuscated powershell running in-memory without touching disk?"
> ok good idea
chat, thats my next paper
> call for papers
> need to do something cool
> something unique
> need ideas
> "hmm... malware only using rpcs?"
> nah
> "hmm.. polymorphic mutation engine?"
> nah
> "self-rewriting polymorphic mutation engine?"
> nah
> "position independent self-rewriting polymorphic mutation engine?"
> nah
> "position independent self-rewriting polymorphic mutation engine with embedded obfuscated powershell?"
> hmmm... maybe
> "position independent self-rewriting polymorphic mutation engine abusing uefi nvram variables in motherboard flash memory with sliding key encrypted embedded obfuscated powershell running in-memory without touching disk?"
> ok good idea
chat, thats my next paper
π₯125β€18π₯°9π€£6π€©3β€βπ₯1π€―1
I have a stupid question
If they do age verification on everyone, making it so only adults can only visit some websites, that pushes people under age to certain parts of the internet that don't require age verification.
... doesn't that make it easier for pedophiles ... ?
If they do age verification on everyone, making it so only adults can only visit some websites, that pushes people under age to certain parts of the internet that don't require age verification.
... doesn't that make it easier for pedophiles ... ?
π€£142π―55π28π€―17π7π€7β€4π₯°3π1
vx-underground
I have a stupid question If they do age verification on everyone, making it so only adults can only visit some websites, that pushes people under age to certain parts of the internet that don't require age verification. ... doesn't that make it easier forβ¦
... like, if the government pushes all the children and teenagers to parts of the internet that don't require age verification ... and all the adults do age verification ... doesn't that just create a massive hangout for children and potential predators ... ? Am I crazy?
π―163π17β€8π7π6π₯°5π€―4
ZachXBT has done some serious shenanigans. Previously, on Dragon Ball Z, ZachXBT noted the discovery of John Daghita a/k/a Lick stealing cryptocurrency from the United States government
His investigative shenanigans got the attention of some dork named Kash Patel.
His investigative shenanigans got the attention of some dork named Kash Patel.
β€46π€£34π₯°7π3π€3π2
vx-underground
ZachXBT has done some serious shenanigans. Previously, on Dragon Ball Z, ZachXBT noted the discovery of John Daghita a/k/a Lick stealing cryptocurrency from the United States government His investigative shenanigans got the attention of some dork named Kashβ¦
For those curious, "Lick" is facing some pretty serious charges. He has successfully racked up the standard cybercrime stuff but with bigger and fancier numbers
- Wire fraud (with a sprinkle of Theft of government property (18 U.S.C. Β§641)): 30 years in prison
- Money laundering: 20 years in prison
- Conspiracy (aggravated, US contractor, position of power).
Under current sentencing guidelines, if "Lick" pleads guilty and begs for forgiveness, he is facing 15 - 30 years in prison. If he walks into the court telling the Judge to suck his dick and starts urinating on the walls, he will receive 50 years in prison.
- Wire fraud (with a sprinkle of Theft of government property (18 U.S.C. Β§641)): 30 years in prison
- Money laundering: 20 years in prison
- Conspiracy (aggravated, US contractor, position of power).
Under current sentencing guidelines, if "Lick" pleads guilty and begs for forgiveness, he is facing 15 - 30 years in prison. If he walks into the court telling the Judge to suck his dick and starts urinating on the walls, he will receive 50 years in prison.
π€£79π₯°20π€8β€3π2π’1
vx-underground
> be kippu > some startup app or something > idfk > goes live > people sign up > realize it's vibe coded > nerds get silly > nerds do http get on api endpoint > dumps entire database *image censored, although it's all over xitter
I don't know what kind of programming logic allows a full DB dump on an HTTP Get, but it is very sophisticated and my little brain just doesn't understand
π€£123β€17π10π₯6π―3π₯°1π€1
Today Donald Trump fired Kristi Noem (lady in charge of DHS) while she was live on television.
I have never seen someone in this prestigious a position fired on live television (or any position, for that matter).
I'm not implying anything with this post.
But, it made me very, very, very, confused. I'm working on this new code thingy, check the internet, and I see this lady fired while she's doing a live press conference, she didn't even know she was fired yet and the banner on the screen says shes fired.
I'm like ???
I have never seen someone in this prestigious a position fired on live television (or any position, for that matter).
I'm not implying anything with this post.
But, it made me very, very, very, confused. I'm working on this new code thingy, check the internet, and I see this lady fired while she's doing a live press conference, she didn't even know she was fired yet and the banner on the screen says shes fired.
I'm like ???
π±64π€£39π₯°7β€5π€―3
vx-underground
Today Donald Trump fired Kristi Noem (lady in charge of DHS) while she was live on television. I have never seen someone in this prestigious a position fired on live television (or any position, for that matter). I'm not implying anything with this post.β¦
Some people asked if I'm trolling. No, I am not trolling, he seriously fired this lady on live tv
π€£114π₯°12π9β€4π±4π2
Big drama on the internet today as someone on Reddit posts a video tutorial on how to perform a self-orchiectomy at home (removal of the testicals).
Please do not perform surgeries on yourself.
Please do not perform surgeries on yourself.
π€£105π±30π€―19π―8β€3π3π₯°3π₯2π€2π2
Because people asked, "what's a Polymorphic Mutation Engine?", we'll talk about it. Truthfully, the name sounds kind of dangerous, or exotic, but in theory and implementation it's not too bad. The primary issue is it requires some prerequisite knowledge and if you don't have it, it gets funky and goopy really fast.
If you're familiar with high-level programming with class inheritance, this is not the same as object oriented polymorphism.
When coding (in literally any language) there is a concept of a mutation engine. As is tradition, it sounds fancy, but if you break it down it makes sense.
What's an engine? If you think of an automobile engine (beep, beep), it's what propels the vehicle forward using a bunch of really small explosions, or something, whatever the fuck "combustion" is.
Likewise, an "engine" in programming is something that takes something in and it results in ... a result.
An engine in a vehicle takes gasoline (something in) and the engine results in "a result" (propulsion, vehicle being able to move). You have a lot of different engines in programming such as search engines, rendering engines, game engines, etc.
In that particular case, a Polymorphic Mutation Engine receives something (code) and then mutates it (changes it). It is called "Polymorphic" because it means Poly (many) - Morph (changes). It changes many times.
If you're familiar with high-level programming with class inheritance, this is not the same as object oriented polymorphism.
When coding (in literally any language) there is a concept of a mutation engine. As is tradition, it sounds fancy, but if you break it down it makes sense.
What's an engine? If you think of an automobile engine (beep, beep), it's what propels the vehicle forward using a bunch of really small explosions, or something, whatever the fuck "combustion" is.
Likewise, an "engine" in programming is something that takes something in and it results in ... a result.
An engine in a vehicle takes gasoline (something in) and the engine results in "a result" (propulsion, vehicle being able to move). You have a lot of different engines in programming such as search engines, rendering engines, game engines, etc.
In that particular case, a Polymorphic Mutation Engine receives something (code) and then mutates it (changes it). It is called "Polymorphic" because it means Poly (many) - Morph (changes). It changes many times.
β€64π₯°2π1π1
vx-underground
Because people asked, "what's a Polymorphic Mutation Engine?", we'll talk about it. Truthfully, the name sounds kind of dangerous, or exotic, but in theory and implementation it's not too bad. The primary issue is it requires some prerequisite knowledge andβ¦
Mutation engines have two different components.
1. The thingy you want to change (code)
2. The thingy that does the changes (the engine).
How you implement both these components is tricky because you have to solve problems such as:
1. Where am I going to store the code that changes?
2. How will the engine make sure each "change" is unique?
Many people have the false belief that a mutation engine means the code changes as it runs, but that isn't necessarily true. While that is technically* possible, it is exceptionally rare and profoundly difficult to implement in any reasonable manner. How self-rewriting code is implemented is outside the scope of this, but it is only achievable with assembly (to the best of my knowledge, I haven't seen it in any other language).
Mutations usually occurs during "mutation events", basically a time when a program can safely change itself without everything imploding. These are usually:
1. Compilation time
2. Infection time
3. ???
Primitive mutation engines change when the binary is compiled. There are many examples of this online. The code is the same, but when you click "build" the result is different each time (the .exe looks different). This is achieved (usually) with a bunch of fancy macros.
More sophisticated mutation engines change code when it infects another program. How this is achieved is also kind of outside the scope of this because it requires a pretty heavy prerequisite knowledge on Microsoft PE files (.exe or .dlls).
??? because this is basically any other time your code can change without is imploding into itself. In my case, with my Polymorphic Mutation Engine, my program changes itself each time it terminates. In other words, when it finishes running and Windows says "ok mr. program go back to the harddrive", this is when my code takes the opportunity to mutate.
1. The thingy you want to change (code)
2. The thingy that does the changes (the engine).
How you implement both these components is tricky because you have to solve problems such as:
1. Where am I going to store the code that changes?
2. How will the engine make sure each "change" is unique?
Many people have the false belief that a mutation engine means the code changes as it runs, but that isn't necessarily true. While that is technically* possible, it is exceptionally rare and profoundly difficult to implement in any reasonable manner. How self-rewriting code is implemented is outside the scope of this, but it is only achievable with assembly (to the best of my knowledge, I haven't seen it in any other language).
Mutations usually occurs during "mutation events", basically a time when a program can safely change itself without everything imploding. These are usually:
1. Compilation time
2. Infection time
3. ???
Primitive mutation engines change when the binary is compiled. There are many examples of this online. The code is the same, but when you click "build" the result is different each time (the .exe looks different). This is achieved (usually) with a bunch of fancy macros.
More sophisticated mutation engines change code when it infects another program. How this is achieved is also kind of outside the scope of this because it requires a pretty heavy prerequisite knowledge on Microsoft PE files (.exe or .dlls).
??? because this is basically any other time your code can change without is imploding into itself. In my case, with my Polymorphic Mutation Engine, my program changes itself each time it terminates. In other words, when it finishes running and Windows says "ok mr. program go back to the harddrive", this is when my code takes the opportunity to mutate.
β€44π₯°9π―4π1π1