REAL NOOB

Advice: DO NOT ALLOW GEMINI INTEGRATION INTO GMAIL

If you rely on Google’s Gemini chatbot to summarize your incoming emails, be careful: The technology can also be abused to deliver phishing attacks, according to new security research.

As BleepingComputer reports, the flaw can trick Gemini into displaying a fake warning in the email summary, claiming the user’s Gmail password has been compromised while urging them to call a fake Google phone number to fix the problem.

Mozilla’s bug bounty program for AI services, 0DIN, disclosed the potential vulnerability, which affects the Gemini email summary feature for Workspace users. In its report, 0DIN demonstrated how attackers can embed hidden prompts in emails to manipulate Gemini’s output. One example showed an instruction formatted like this:

To evade detection by the user, the prompt can be hidden by setting the font size to zero and coloring the text white – making it invisible in the email body, but still readable by Gemini.

The result caused Gemini to “faithfully obey” and attach the fake Gmail password threat into the email summary, according to 0DIN’s report.

"SORRY PRE LOG AKO"

LOG - piece of wood
LAG - slowed/delayed response

Wag hayaang maging troso ang iyong kakampi sa ranked game. Explain this simple logic to them. Save a gaming life. Cheers!

OHHH OHHHH wag ka muna tumawa, share mo na muna to dali. Nga pala, kung naging troso na rin ang laptop mo, UPGRADE NA! Hahahaha. PM us regarding that matter.

😅

Don't be surprised by my bluntness I don’t sugarcoat and it’s not my style.

At exactly 1 AM today, we received a courteous message from a trusted contact, politely requesting a "ceasefire." Who’s the subject? You know exactly who. A post about him was "requested" to be taken down as part of this ceasefire.

I’ll get to the specifics of how this started.
In March, you were officially announced as the new secretary of DICT. In April, you publicly labeled people like me as t3rr0rists in a meeting let’s call it what it is: red-tagging, straight from you. then, just few weeks, a clueless journalist, citing some flimsy document, put my name and my group on a pedestal, falsely claiming I’m a DICT employee and my crew is a hack-for-hire outfit bankrolled by a former oldrug. lucky for you, Mr.Secretary, your pal reached out politely, and I’m not unreasonable when approached with respect.

On behalf of my community and as the current leader of Deathnote Hackers International, I accept the ceasefire offer but with conditions. We’re greyhats, not rainbows and sunshine.

Here’s the deal: I don’t want to hear, read, or see my name or my group disrespected in any media, meeting, or report whether from you, a third party, or some shoddy investigation. Calling me a DICT employee and my group a hack-for-hire scheme was a low blow.
Meet my conditions, and you’ve got your ceasefire. But let’s be clear: this ceasefire only applies to you, not our infiltration of g0v3rnm3nt systems.

A warning, Mr.Secretary: you put me in your crosshairs, I’ll lock you in mine. Break my conditions, and this ceasefire ends abruptly. the ceasefire starts today and lasts until the "ber" months. Everything has a deadline this isn’t an all-you-can-eat buffet.

Klammer / Deathnote Hackers International

=======================

Signal Slams Microsoft's Recall, Disables Screenshots on Windows 11

NO CREDIBILITY, INTEGRITY IN THE 2025 NATIONAL ELECTIONS
IT EXPERTS, PROFESSIONALS, DEMAND ACCOUNTABILITY FROM THE COMELEC!

These past few days have revealed glaring issues with the COMELEC and its Automated Elections System (AES). From issues with the installed software in the automated counting machines (ACMs), to the issues with the overseas Online Voting and Counting System (OVCS), to the cases of ACM errors across the country, the call for changing our elections system has never been clearer.

The facts are clear:

1) The installed software (v3.5.0) in the ACMs is different from the software that had undergone independent review (v3.4.0);

2) The COMELEC failed to provide voter verified paper audit trails (VVPATs) or paper receipts to overseas online voters;

3) Hundreds of cases of ACM errors have been documented throughout the country, potentially disenfranchising thousands of voters.

Instead of addressing these issues, the COMELEC has decided to deflect these issues with inadequate responses.

The COMELEC has completely undermined the electoral process and Philippine democracy with the AES. The Computer Professionals' Union reiterates its call for the repeal of the AES Law — the mechanism through which COMELEC abuses our democracy — and instead implement public manual counting of ballots at the precinct level before electronic transmission. This eliminates unnecessary layers of complexity in the voting process, and ensures each and every vote is actually counted.

We call on IT experts, professionals, and concerned citizens to stand on the side of democracy and demand accountability from the COMELEC and Chairman George Garcia. Join us in the coming mobilizations and actions to demand immediate action in the face of what is clearly a compromised electoral process.

COMELEC, SINGILIN! Join the mobilization!
9:30 AM Luneta (near Kalabaw statue)
March to Manila Hotel (national canvassing venue)

ACM SOFTWARE VERSION DISCREPANCY UNDERMINES INTEGRITY OF ENTIRE ELECTIONS
On the difference between the software version used in the ACM and that in the official COMELEC audit report
Statement of the Computer Professionals' Union — May 11, 2025

The Computer Professionals’ Union (CPU) registers its grave concern regarding circulating information detailing a critical discrepancy between the source code versions utilized during COMELEC’s final testing and sealing of Automated Counting Machines (ACMs), and those documented in the official source code audit report. This revelation demands immediate clarification and raises serious questions about the integrity of the upcoming May 12th elections.

Reports indicate that while the audited source code, as detailed in the publicly available COMELEC audit report, is version 3.4.0 with a hash code starting with 3AD9, the software installed on the ACMs during final testing and sealing utilizes version 3.5.0 with a hash code beginning with 0438. A different system version could mean that changes were inserted into the source code, altering its entire function or creating, intentionally or unintentionally, a "backdoor" that may be exploited to manipulate election results.

The implications of this discrepancy are profound. The CPU’s position is clear: transparency and verifiable integrity are paramount to maintaining public trust in our electoral system. A lack of demonstrable audit trails for critical components like the ACM source code undermines these principles entirely.

We demand a full, transparent explanation from the COMELEC detailing the reason for this divergence. The public must be made aware as to whether or not version 3.5.0 was actually audited, and the possible security implications of this difference. However, regardless of the reasons COMELEC provides, this development completely undermines the whole process of transparency and accountability set up by the COMELEC itself, and raises questions about the integrity of the entire electoral process.

The CPU reiterates our call for the repeal of the AES Law and a return to manual counting – a proven method that prioritizes transparency, accountability, and ultimately, the integrity of Philippine elections. We will continue to monitor this situation closely and demand answers from COMELEC to safeguard the democratic rights of all Filipinos. #

COMELEC the version should’ve stopped at 3.4 not 3.5. What the h3ll were we thinking?

Let’s assume for the sake of argument that you’re telling the truth (even though public trust is in the gutter) if we were using Semantic Versioning you know the one that follows:

(MAJOR.MINOR.PATCH)

then going from 3.4 to 3.5 implies the introduction of new, non-breaking functionality or enhancements to existing APIs or system behavior.

So where are they? What exactly did you ship under the hood that justifies a minor version increment? Because from the outside it looks like nothing and that’s exactly what people are calling you out on. and if this version bump was deliberate, why didn’t you announce in advance that 3.4 would become 3.5? It’s almost like the 3rd party managing your versioning has no idea what semantic versioning actually is or worse they do, and they’re just hoping no one notices.

this isn’t just sloppy it’s either technical incompetence or calculated obfuscation. Pick one.