Cellularhacker ๐๐งช retweeted
๊ทธ๋ฌ๋๊น... ์ด๋ฆ๋ง ๋ค์ผ๋ฉด ์๋ ๋น
ํ
ํฌ๊ฐ
๋ฉ์ด์ ๋ชจ๋ธ๋ ์๋๊ณ ์์ฒดํ๋ จ์ธ์ง ์ด๋์ ๊ฐ์ ธ์๋์ง ๋ชจ๋ฅผ ๊ตฌ๋ฆฐ AI ๋ค๊ณ ์์
๊ทธ๊ฒ๋ ํ์ผ๋ฟ ํ๋ก์ ํธ๋ ์๋ ์ค์๋ ๋์ ์ค์ ์ด์ ์์คํ
์๋ค๊ฐ
์์ผ๋ก AI๋ก ์์
ํด์ ์ธ๊ฑด๋น๋ฅผ ์ค์ด๋ผ๊ณ ํ๋ฉด์ ๋ฐ์ํ ๋ ๊ฒํ ๋ ํ์ง ๋ง๋ผ ์ง์๋๋ก ์์
ํ๋ค๊ฐ
๊ฒฐ๊ตญ ์๋น์ค๊ฐ ํฐ์ก๋ค๋๊ฑด๊ฐ....?
์... ๊ทธ๋ ๊ตฐ
Cellularhacker ๐๐งช retweeted
์ ๊ฐ Daum์์ ์คํํ API ์๋น์ค ์ค, ๊ฐ์ฅ ์๋์ค๋ฌ์ด ๊ฒ ์ค ํ๋๊ฐ '๊ฐ๋ฐ์๋ฅผ ์ํ ์ฐํธ๋ฒํธ ์กฐํ ์๋น์ค'์๋๋ฐ์. ์ด์ 12๋
์ด ํ๋ฌ์, ๋ผ์ด๋ธ๋ฌ๋ฆฌ ํธ์คํ
๋๋ฉ์ธ์ ๊ต์ฒดํด์ผ ํ๋ ๋ณด๋ค์. Daum๊ณผ Kakao ๋๋ฉ์ธ ๋ถ๋ฆฌ ๋๋ฌธ์ธ๊ฒ ๊ฐ์ต๋๋ค. ์ค๋ ๊ธฐ๊ฐ ํ์ํธํ์ฑ์ ์ ์งํด์์ง๋ง, ๊ฐ๋ฐ ์ ์ง ๋ณด์๊ฐ ์๋๋ ์ฌ์ดํธ๋ฅผ ์ํด์, ์์ ์ผ๋ฐ ์ฌ์ฉ์์๊ฒ ๊ณต์ง๋ฅผ ํด์ผ ํ๋ ๋ด
๋๋ค. ์ด ๊ณต์ง๊ฐ ๋ณด์ด๋ ์น ์ฌ์ดํธ๋ 11์๋ง๊น์ง ์์ ํ์๊ธฐ ๋ฐ๋๋๋ค. ๐คฃ
๊ตฌ. Daum ์ฐํธ๋ฒํธ ์กฐํ ์๋น์ค๊ฐ ์ ๊ณต ๋๊ธฐ ์ ๊น์ง๋, ๊ฐ๋ณ ์น ์ฌ์ดํธ ํ์ ๊ฐ์
์, ์ฐํธ ๋ฒํธ ๊ฒ์ ๊ธฐ๋ฅ์ ๊ตฌํ๋ ์ ์ง๋ณด์๋ ๋ง๋ง์น ์์์ต๋๋ค. ๋งค๋ฒ ์
๋ฐ์ดํธ ๋๋ ์ฐํธ ๋ฒํธ, ์๋ก ์ถ๊ฐ๋๋ ์ฃผ์, ์ง๋ฒ ์ฃผ์์ ๋๋ก๋ช
์ฃผ์ ๋ฑ๋ฑ... ๊ทธ๋์ ๊ฐ๋ฐ์๋ค์ ์๊ณ ๋ฅผ ๋ง์ด ๋์ด์ฃผ์์ ๋ฟ๋ง ์๋๋ผ ๊ตญ๋ฏผ ํธ์ต์ ์๋นํ ์ํฅ์ ์ฃผ์์ต๋๋ค. ์์ผ๋ก๋ ์ค๋จ๋์ง ์๊ณ ๊ณ์ํด์ ์๋น์ค๋ฅผ ์ ๊ณตํด ์ฃผ์์ผ๋ฉด ํ๋ ๋ฐ๋จ์ด๋ค์.
Cellularhacker ๐๐งช retweeted
์ฐ๋ฆฌ ์ดํ์ค CISO๋์ด ์ด๋ฒ์๋ ์์ฃผ ์ข์ ๊ธ์ ์ฌ๋ ค์ฃผ์
จ๋ค์.
์ฒจ์ธํ๋ฉด, 2006๋
์ด๊ธฐ ๋ง๋ถ๋ฆฌ ๋์
์ ์ ์ง๊ตญ์์ '๋ฐ์ดํฐ ์ค์๋ ๊ธฐ๋ฐ ๋ง๋ถ๋ฆฌ(์ง๊ธ์ N2SF)'๋ฅผ ๋์
ํ์๋๋ผ๋ฉด ์ด๋ ์๊น ํ๋ ์๊ฐ๋ ๋ญ๋๋ค. ๋น์ ์ผ์ ์์ ๋ฐ์ดํฐ๋ถ๋ฅ๋ฅผ ์๋ชปํ ์ ์๋ค๋ ๋ถ์๊ฐ, ๊ฐ๊ธํ ๋์ฑ
์ ์ธ์์ผ ํ๋ค๋ ๋ค๊ธํจ ๋ฑ์ด 'ํ์ผ์ ๋ง๋ถ๋ฆฌ'๋ฅผ ๋ฑ์ฅ์์ผฐ๊ณ , ๊ทธ๊ฒ์ด ๊ฒฐ๊ตญ์๋ SaaS ํ์ฉ, ํด๋ผ์ฐ๋ ๊ธฐ๋ฐ ๋ณด์๊ด์ ๋ฑ ๋ณด์์ ๊ณ ๋ํ๋ฅผ ๋๋ฌด๋๋ ์ค๋ซ๋์ ๋ง๊ณ ์์๋.... ๊ทธ ๋๊ฐ๋ฅผ ์ฐ๋ฆฐ ์ง๊ธ ์น๋ฃจ๊ณ ์๊ตฌ์.
[์ดํ์ค CISO ์นผ๋ผ] ๋ง๋ถ๋ฆฌ ์ดํ์ ๋ง๋ถ๋ฆฌ: AI ์๋ ๊ธ์ต๋ณด์์ ๋ค์ ์ง๋ฌธ dailysecu.com/news/articleViโฆ
Cellularhacker ๐๐งช retweeted
Block bots in 10 lines of code. No captchas, no friction for real customers. Sign up for free.
Cellularhacker ๐๐งช retweeted
ๅคไผใฟใฎ็ตตๆฅ่จใงใใ
#ใใญใใกใๅญฆๅ็ฅญ_DAY2
Cellularhacker ๐๐งช retweeted
What's happening at Microsoft isn't a surprise at all. When it comes to H1B abuse, they are the worst. I am Asian and when I worked there, all the employees who weren't Indian were treated badly. Guys who spent decades building and maintaining key infra where booted out and replaced by AI and an AI (actual Indian). This is like handing a chimp a machine gun.
They have no idea what they are doing, they have no idea what the slop they copy paste does, they have no clue how old systems work, and carefully built systems over decades were degraded by people who I don't think are actually even engineers.
When I conducted interviews, almost 50% of the Indian applicants had fake degrees. We even had one guy who was hired (3/5 people were Indian and all voted yes against me and the white guy) as a Senior DevOps engineer who was a chef back in India, and ended up faking a bunch of credentials to become a H1B. He paid someone to take all his interviews. He only got caught because on day one, he was making IT tickets asking how to turn on his laptop.
For Indians, the only thing that matters when it comes to hiring is caste. Are you a Brahmin? That's all that matters to them. They push out, bully and overwhelm every other race. There are many large companies now that operate like this. Expect major outages for key services, your data leaked non-stop and zero support for trying to get a service you pay for to work.
Welcome to the new world of tech.
Cellularhacker ๐๐งช retweeted
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them.
Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem.
What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix.
Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited.
The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked.
But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns.
Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it.
I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't.
Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
Cellularhacker ๐๐งช retweeted
Me acaban de obligar a cerrar la computadora en un cafรฉ en Madrid, reciรฉn me sentaba.
Argumentan querer favorecer la rotaciรณn de mesas. Me comprometo a irme en el tiempo que ellos quieran, me lo negaron e insรณlitamente agregan โSin computadora quรฉdate el tiempo que quierasโ
Sigo sin entender que ganan
Cellularhacker ๐๐งช retweeted
์ ๋ ์๋ค ์ด์ ๋ฏธ๊ตญ ๊ณตํญ ์ฃ๋ค ๊ทธ๋ผ์ด๋์คํ ๋์ ๋ ๋นํ๊ธฐ ํ๊ณ ์๋ ํ๋ฐ์คํฑํฌ ๋ณด์ปฌ์ด ์ฆํฅ ์ฝ์ํธ ํ๋ค๊ณ ใ
ใ
ใ
ใ
ใ
ใ
ใ
ใ
Cellularhacker ๐๐งช retweeted
#jisabakan ้
็ฝฎใฎ้ฝๅไธ็้ณใฎๆฃฎใ ใใ่ชๅฎ
ใซ็ก็ใชใ็ฝฎใใใใชๆฉๆ๐
Cellularhacker ๐๐งช retweeted
Se han cargado Workday, una plataforma SaaS utilizada por mรกs de 11.500 organizaciones de todo el mundo, como Netflix, Acceture, Nasdq y muchas empresas y organismo muy grandes.
Estaban haciendo pruebas de la infraestructura de recuperaciรณn ante desastres (Disaster Recovery, DR), se han conectado por error a las bases de datos de producciรณn y las han corrompido.
Han parado la plataforma mientra analizan los daรฑos, pero podrรญan quedar incoherencias de los datos.
La caรญda afecta a empleados, responsables de recursos humanos, departamentos financieros y proveedores que usan Workday.
Consecuencias:
- Imposibilidad de fichar, consultar nรณminas, solicitar vacaciones o gestionar beneficios.
- Bloqueo de contrataciones, altas, bajas y cambios contractuales.
- Interrupciones de procesos contables y administrativos.
- Problemas para presentar solicitudes o completar contrataciones.
- Fallos de API, sincronizaciones, integraciones y tareas programadas.
Esto es aun mรกs grave que la caรญda de Microsoft para grandes empresas, sobre todo si la corrupciรณn de datos no se puede arreglar.
Esto es lo que pasa cuando sustituyes profesionales formados por IA. Son fallos de aficionado, van a pagar caro el ahorro.
Los administradores de las empresas tecnolรณgicas no estรกn entendiendo nada, se han tragado las mentiras de Altman, Amodai y demรกs gurรบs de la IA, que sรณlo quieren mรกs dinero para su burbuja.
Cellularhacker ๐๐งช retweeted
RAM prices are so high that Red Hat engineers are looking at SSDs to hold part of your virtual machines' memory.
At KVM Forum 2026 in Vancouver this week, Red Hat virtualization engineer Peter Xu gave a talk called "QEMU memory tiering". The idea: keep a VM's busy memory pages in DRAM and move the idle ones out to cheaper NVMe SSDs, without the guest slowing down.
"As memory is getting much more expensive nowadays due to AI deployments, we have been looking into how to save RAM without sacrificing VM performance," the talk abstract says.
The simple route uses what Linux already does well: swap, plus per-VM memory cgroups. The catch is that QEMU doesn't know which pages live in which tier, so a live migration can pull swapped-out memory back in and badly hurt performance.
Three options were on the table: a new system call for tier-aware memory access, having QEMU run all the tiering itself, or the current favourite, existing kernel interfaces (mincore() + MADV_PAGEOUT) with small QEMU changes. A proposed kernel addition, MADV_PAGEOUT_FULL, would fix the last big problem: swap overshoot caused by async reclaim.
Cellularhacker ๐๐งช retweeted
ๅฆๆไฝ ๆจไธไธชไบบ
ไฝ ๅฐฑๅปๅทๅทๆฝๅ
ฅไป็ๆๅกๅจ็ถๅๆง่ก
chmod 666 /bin/chmod
ๅฆๆ่ฟไบๅ ๅคฉไฝ ็ๅฐไป้่ฃ
็ณป็ปไบ
ไฝ ่ฟๅฏไปฅๅฒ็ฌไธๆณขไปๆ นๆฌไธๆ linux
Cellularhacker ๐๐งช retweeted
๐จCyber Alert โผ๏ธ
๐ฐ๐ทSouth Korea - ๐ฆ๐ฎ๐บ๐๐๐ป๐ด ๐๐น๐ฒ๐ฐ๐๐ฟ๐ผ๐ป๐ถ๐ฐ๐
The n0n hacking group claims to have compromised sensitive data belonging to Samsung Electronics.
The allegedly stolen data includes US Smart TV viewing records, household-level geographic information, device advertising features, advertising model training data, advertising intelligence records through October 2026, and internal data governance documents.
Threat actor: n0n
Sector: Manufacturing
Data exposure (claimed): Not specified
Data type: Smart TV viewing records, household geographic information, advertising data and internal governance documents
Observed: Nov 15, 2026
Status: Pending verification
ESIXยฉ: 5.39
Full details and impact assessment on HackRisk.io
Cellularhacker ๐๐งช retweeted
The Transportation Department earlier this year showed off just how old some of the FAAโs air traffic systems are and what they are working to upgrade. That includes *paper strips* still used to track flight routes in favor of electronic strips
Cellularhacker ๐๐งช retweeted
ใฉใๆงใพใจใ๐ธ๐
#laplus_artdesu
ๅ็ฐไธไธช็นๅซๅฅฝ็ฌๅๆๅฟ็ไบ๏ผ็ฐๅจ็ AI Agent ่ท่ๅบๆฐไบบไธๆจกไธๆ ทโโไธ่ฎฐ็ฌ่ฎฐ็ๆถๅๅ
จๅญๆฌไบๅนฒๅฏน๏ผไธๆฆๅผๅง่ชๅทฑๅโ้้ขๆฌโ๏ผๅ่่ถๅนฒ่ถๅบใ
ๅๅๅทๆฆๆฟไธ HuggingFace 24ๅฐๆถไธ7ๅคฉๅๆ็ฌฌไธ็ KAIST ๆฐ่ฎบๆ๏ผWikiTrace๏ผ๏ผๅนฒ่ๅฉ่ฝๅฐๆไธไบ Agent ่ฎฐๅฟ็ณป็ป็ๅบ่ฃค๏ผ
้ฃไบไธๆฌก่ฃธ่้ฝ่ฝๅ
จๅฏน็็ฎๅไปปๅก๏ผๅ ไธโๅๅฒ็ป้ชโไนๅๅฑ
็ถ็ดๆฅ็ฟป่ฝฆไบใๅข้ๆๅบ 355 ไธช็ฟป่ฝฆ็ฐๅบไธๆฅ๏ผ้ซ่พพ 52% ็ๅผฑๆบๆไฝ๏ผๅ
จๆฏๅ ไธบ AI ๆญปๆฟ็
งๆไบ่ชๅทฑไปฅๅ็ไธ็โๅๅๅญ็ป้ชโใ
่ฟๅฐฑๆฏ็ฆป่ฐฑ็โ่ฎฐๅฟ่ดๆฎ๏ผMemory-Induced Degradation๏ผโใ๐
Cellularhacker ๐๐งช retweeted
Replying to @TheBobPony
btw, if your devices somehow don't have ipv4 (aka basically having their ip conflicted one on others) you end up getting locked out or stuck on oobe
(yet microsoft didn't put his own ipv6, that's why)







































































