Torba needs your real IP address, user name and some money so you can look at a random #gab post somebody shared...
Andrew Torba And The Grift Of Gab
https://providencepost.com/torba-grift-of-gab/
********
👉🏼 Andrew Torba, Thiel Network (+ scrollllll) 👈🏼
Torba- "I'm all in on Trump..."
Torba celebrating the technocrat takeover of the right
Nothing more genuine than AI astroturfing the "Christian Nationalism movement"...
Doesn't add up, huh? Or maybe it adds up perfectly. (Torba, Dershowitz)
Andrew Torba And The Grift Of Gab
https://providencepost.com/torba-grift-of-gab/
********
👉🏼 Andrew Torba, Thiel Network (+ scrollllll) 👈🏼
Torba- "I'm all in on Trump..."
Torba celebrating the technocrat takeover of the right
Nothing more genuine than AI astroturfing the "Christian Nationalism movement"...
Doesn't add up, huh? Or maybe it adds up perfectly. (Torba, Dershowitz)
Forwarded from The Cradle
Media is too big
VIEW IN TELEGRAM
WATCH | Qassam Brigades publishes a video titled, "The occupying government has decided to starve them. Time Is Running Out..."
https://linuxmint.hu/hir/2025/08/ujabb-rosszindulatu-program-az-arch-aur-ban
Another Malware Found in Arch AUR
Another Malware Found in Arch AUR: Another Malicious Code Found in the Popular Package Repository
Just ten days after the previous incident, another malicious software was found among the Arch Linux AUR packages. This time, the attackers hid a Remote Access Trojan (RAT) in a seemingly harmless package disguised as a browser.
What exactly happened?
The AUR (Arch User Repository) is a collection of software created by the Arch Linux community and maintained by users, which many consider to be one of the greatest advantages of Arch, almost a “hidden treasure”. However, due to its completely open upload system, it can also become a target for malware.
After the previous incident ten days ago, a Remote Access Trojan (RAT) has now been added to the package repository. This time, the malicious code was hidden in a package called google-chrome-stable. The package not only installed the Google Chrome browser, but also used a Python script to download and run an external resource containing the malicious code every time it was started.
This type of malware can give attackers full access to the infected machine, allowing them to steal data, install additional malicious software, or even spy on it.
How did the package get uploaded?
The problematic package was uploaded by a newly registered user under the username “forsenontop”. In the PKGBUILD file, an install script (google-chrome-bin.install) called a launcher script (google-chrome-stable.sh) that ran a Python command with the -c option before Chrome was launched. This command pulled in an external resource on every launch, which downloaded the malware.
The good news is that the package was only available in the AUR for a few hours before it was detected and immediately removed by administrators. However, it still received a few upvotes, suggesting that several users may have already installed it.
What should affected users do?
If someone has installed the malicious package, they should immediately remove it and run a full security scan on their system. However, experts in the Arch community say that the safest solution is a full system reinstall (OS preinstall) to rule out any backdoors or hidden malicious code.
What’s the lesson?
This incident once again highlights that while the AUR is an extremely useful resource, the security of packages is not the responsibility of the official Arch Linux developers, but rather the community.
The incident clearly demonstrates how easy it is to upload a legitimate-looking package using a fake account. That’s why it’s important for users to always check the history of a package:
Check how long the package has been around.
Check the uploader’s reputation and the contents of the PKGBUILD file.
Avoid freshly uploaded packages with no history, even if the name seems official.
Browsers, as in the previous incident, are a particularly attractive target for attackers, as they are among the most widely used software.
Strengthen your future protection
Always check the PKGBUILD contents before installing:
yay -G packagename cd packagename less PKGBUILD
Avoid newly uploaded packages. If the AUR package has no history or reviews, it is not recommended to install it.
Another Malware Found in Arch AUR
Another Malware Found in Arch AUR: Another Malicious Code Found in the Popular Package Repository
Just ten days after the previous incident, another malicious software was found among the Arch Linux AUR packages. This time, the attackers hid a Remote Access Trojan (RAT) in a seemingly harmless package disguised as a browser.
What exactly happened?
The AUR (Arch User Repository) is a collection of software created by the Arch Linux community and maintained by users, which many consider to be one of the greatest advantages of Arch, almost a “hidden treasure”. However, due to its completely open upload system, it can also become a target for malware.
After the previous incident ten days ago, a Remote Access Trojan (RAT) has now been added to the package repository. This time, the malicious code was hidden in a package called google-chrome-stable. The package not only installed the Google Chrome browser, but also used a Python script to download and run an external resource containing the malicious code every time it was started.
This type of malware can give attackers full access to the infected machine, allowing them to steal data, install additional malicious software, or even spy on it.
How did the package get uploaded?
The problematic package was uploaded by a newly registered user under the username “forsenontop”. In the PKGBUILD file, an install script (google-chrome-bin.install) called a launcher script (google-chrome-stable.sh) that ran a Python command with the -c option before Chrome was launched. This command pulled in an external resource on every launch, which downloaded the malware.
The good news is that the package was only available in the AUR for a few hours before it was detected and immediately removed by administrators. However, it still received a few upvotes, suggesting that several users may have already installed it.
What should affected users do?
If someone has installed the malicious package, they should immediately remove it and run a full security scan on their system. However, experts in the Arch community say that the safest solution is a full system reinstall (OS preinstall) to rule out any backdoors or hidden malicious code.
What’s the lesson?
This incident once again highlights that while the AUR is an extremely useful resource, the security of packages is not the responsibility of the official Arch Linux developers, but rather the community.
The incident clearly demonstrates how easy it is to upload a legitimate-looking package using a fake account. That’s why it’s important for users to always check the history of a package:
Check how long the package has been around.
Check the uploader’s reputation and the contents of the PKGBUILD file.
Avoid freshly uploaded packages with no history, even if the name seems official.
Browsers, as in the previous incident, are a particularly attractive target for attackers, as they are among the most widely used software.
Strengthen your future protection
Always check the PKGBUILD contents before installing:
yay -G packagename cd packagename less PKGBUILD
Avoid newly uploaded packages. If the AUR package has no history or reviews, it is not recommended to install it.
🇺🇸 Trump deploys nuclear submarines because Medvedev was rude
Trump:
He's shitposting all the time … LMAO
🔗
➡️ Join us! | @MyLordBebo
Trump:
"Words are important and can lead to unintended consequences"
He's shitposting all the time … LMAO
🔗
➡️ Join us! | @MyLordBebo
Lindsey threatens to nuke, bomb and destroy a country once a week … he should sit down.
🔗
➡️ Join us! | @MyLordBebo
🔗
➡️ Join us! | @MyLordBebo
🇷🇺🇺🇸 The head of Roscosmos Bakanov and the acting head of NASA Duffy agreed to operate the ISS until 2028.
🔗
➡️ Join us! | @MyLordBebo
🔗
➡️ Join us! | @MyLordBebo
“NASA representatives discussed with their Roscosmos colleagues the possibility of rescuing each other's crews”
— NASA Deputy Administrator Kenneth Bowersox.
If a situation arises where a spacecraft from any country encounters a problem, and another country has a spacecraft available, they will be able to help each other.
🔗
➡️ Join us! | @MyLordBebo
#EU's new cybersecurity rules will impact #Android starting August 1, 2025. #Bootloader unlocking will likely be banned, limiting user control and custom ROM installations. #Samsung has already removed this feature in OneUI 8. A major shift for Android in Europe!"
https://xiaomitime.com/eu-kills-android-bootloader-unlock-starting-august-1-59449/
@xiaomiui
This is clickbait. There is no clause requiring to block bl unlock. There is stuff such as check to make sure updates are secure.
Samsung did remove it because they suck, but this wasn't a legal requirement.
https://xiaomitime.com/eu-kills-android-bootloader-unlock-starting-august-1-59449/
@xiaomiui
This is clickbait. There is no clause requiring to block bl unlock. There is stuff such as check to make sure updates are secure.
Samsung did remove it because they suck, but this wasn't a legal requirement.
XimiTime
Don’t panic: EU isn’t ending bootloader unlocks anytime soon - XimiTime
There’s been a significant amount of noise circulating online lately about the European Union’s Radio Equipment Directive (RED) and its supposed impact on
The AndroidFileHost was abandoned in 2023 and went offline a few weeks ago due to that a lot of Android development history, custom ROMs, kernels, gapps, etc. has been lost.
So, a reddit user has created AFHArchive, a site dedicated to preserving the files that were once hosted on AndroidFileHost. While uploading large files, just include as much info as you can, and after a review by the admins, they’ll be published for everyone to access again.
NOTE: AFHArchive is dedicated to preserving files that were previously hosted on AndroidFileHost.
• Only upload files that were once on AFH
• Provide original AFH links when possible
• Include device information & XDA threads
• All uploads require admin approval
• New builds or custom ROMs will not be approved
Follow @TechLeaksZone
So, a reddit user has created AFHArchive, a site dedicated to preserving the files that were once hosted on AndroidFileHost. While uploading large files, just include as much info as you can, and after a review by the admins, they’ll be published for everyone to access again.
NOTE: AFHArchive is dedicated to preserving files that were previously hosted on AndroidFileHost.
• Only upload files that were once on AFH
• Provide original AFH links when possible
• Include device information & XDA threads
• All uploads require admin approval
• New builds or custom ROMs will not be approved
Follow @TechLeaksZone
Reddit
From the androidroot community on Reddit
Explore this post and more from the androidroot community