Forwarded from govd
source - @govd_bot
Anthropic accidentally leaked the source code for Claude Code via a public npm source map, exposing ~500K lines across ~1,900 files.
It doesn’t include the model itself no weights or training data but reveals how Anthropic builds its tools and agent workflows.
GitHub link: https://github.com/instructkr/claude-code
🔥3
Forwarded from Tech & Leaks Zone
BREAKING: Nekogram is secretly transmitting your telegram account phone number to the developer
According to SOTA,
"The backdoor is hidden in the http://Extra.java file, which differs from the template uploaded to the repository. The obfuscated code sends data as an inline request to the @nekonotificationbot, leaving no trace. The same file implements account 'doxing' via several bots; it is possible that the leaked data is used to populate their databases."
Additionally, the creator of the Nekogram client, (presumably a Chinese national) was previously known for conducting DDoS attacks and unethical online behavior (including death threats against acquaintances).
Apparently, in the early versions of the client, de-anonymization was applied only to Chinese phone numbers, which could have been used for political surveillance;. However, it is now applied to all users.
Follow @TechLeaksZone
According to SOTA,
"The backdoor is hidden in the http://Extra.java file, which differs from the template uploaded to the repository. The obfuscated code sends data as an inline request to the @nekonotificationbot, leaving no trace. The same file implements account 'doxing' via several bots; it is possible that the leaked data is used to populate their databases."
Additionally, the creator of the Nekogram client, (presumably a Chinese national) was previously known for conducting DDoS attacks and unethical online behavior (including death threats against acquaintances).
Apparently, in the early versions of the client, de-anonymization was applied only to Chinese phone numbers, which could have been used for political surveillance;. However, it is now applied to all users.
Follow @TechLeaksZone
Forwarded from Tech & Leaks Zone
EXPOSED: Source Code Evidence of Nekogram Phone Number Harvesting
1. Exfiltration Logic: The function uo5.g() (reconstructed as logNumberPhones) silently collects the UserID and Phone Number of every account logged into the app (up to 8 accounts).
2. Transmission: Data is sent via Inline Queries to the bot @nekonotificationbot. This is done programmatically, so no message appears in your "Sent" history.
3. Target Bots: Three bots embedded in the client's obfuscated code:
@nekonotificationbot: Receives the automated phone number uploads.
@tgdb_search_bot and @usinfobot: : An OSINT bot mentioned in the obfuscated classes.
4. Security Token: The app uses a hardcoded secret key 741ad28818eab17668bc2c70bd419fc25ff56481758a4ac87e7ca164fb6ae1b1 as a prefix for the stolen data, likely to authenticate with the bot's backend.
5. The image shows that Nekogram always wants to get the "reg date".
Unfortunately the Google Play Store version is also affected!!!
Follow @TechLeaksZone
1. Exfiltration Logic: The function uo5.g() (reconstructed as logNumberPhones) silently collects the UserID and Phone Number of every account logged into the app (up to 8 accounts).
2. Transmission: Data is sent via Inline Queries to the bot @nekonotificationbot. This is done programmatically, so no message appears in your "Sent" history.
3. Target Bots: Three bots embedded in the client's obfuscated code:
@nekonotificationbot: Receives the automated phone number uploads.
@tgdb_search_bot and @usinfobot: : An OSINT bot mentioned in the obfuscated classes.
4. Security Token: The app uses a hardcoded secret key 741ad28818eab17668bc2c70bd419fc25ff56481758a4ac87e7ca164fb6ae1b1 as a prefix for the stolen data, likely to authenticate with the bot's backend.
5. The image shows that Nekogram always wants to get the "reg date".
Unfortunately the Google Play Store version is also affected!!!
Follow @TechLeaksZone
😭1
Forwarded from 🌱 Activacy
BrowserGate
LinkedIn Is Illegally Searching Your Computer
Microsoft is running one of the largest corporate espionage operations in modern history. Every time any of LinkedIn’s one billion users visits linkedin.com, hidden code searches their computer for installed software, collects the results, and transmits them…
Forwarded from Worst Timeline (sakros esed)
Una piccola lista non esaustiva di vendor alternativi per computer e altri device Linux. Se ne conoscete altri li aggiungo.
Nota: non ho verificato affidabilità né qualità
Prevalentemente laptop / desktop / x64
• Slimbook — ES
• TUXEDO Computers — DE
• Laptop with Linux — NL
• Star Labs — UK
• framework — USA
• system76 — USA
• Purism — USA
• Kubuntu Focus (MindShare) — USA
Prevalentemente SBC / altro
• Zima (IceWhale) — CH
• LattePanda — CH
• Pine64 — HK
• Raspberry Pi — UK
Nota: non ho verificato affidabilità né qualità
Prevalentemente laptop / desktop / x64
• Slimbook — ES
• TUXEDO Computers — DE
• Laptop with Linux — NL
• Star Labs — UK
• framework — USA
• system76 — USA
• Purism — USA
• Kubuntu Focus (MindShare) — USA
Prevalentemente SBC / altro
• Zima (IceWhale) — CH
• LattePanda — CH
• Pine64 — HK
• Raspberry Pi — UK
🔥5
Ora posso controllare la TV del salotto stando comodamente seduto in camera, oppure da telefono, oppure da internet appena metto wireguard
Sto cercando di migrare da Syncthing a Syncthing-Fork, peccato che gli sviluppatori abbiano rimosso la possibilità di importare dal vecchio formato di configurazione
https://forum.syncthing.net/t/syncthing-fork-new-config-format-prevents-migration-from-legacy-syncthing-app/24496
Quindi mi tocca
• fare un backup sull'app originale (non più mantenuta)
• installare il fork 1.28.1(che si trova SOLO qui)
• importare
• aggiornare a 1.30.0(uguale, grazie izzysoft)
• esportare di nuovo
• disinstallare l'app (hanno cambiato package id...)
• installare l'ultima versione
• reimportare
Edit: ok, la vecchia versione è presente nei repo FDroid come "Syncthing-Fork v1"
https://forum.syncthing.net/t/syncthing-fork-new-config-format-prevents-migration-from-legacy-syncthing-app/24496
Quindi mi tocca
• fare un backup sull'app originale (non più mantenuta)
• installare il fork 1.28.1
• importare
• aggiornare a 1.30.0
• esportare di nuovo
• disinstallare l'app (hanno cambiato package id...)
• installare l'ultima versione
• reimportare
Edit: ok, la vecchia versione è presente nei repo FDroid come "Syncthing-Fork v1"
Syncthing Community Forum
Syncthing-fork: New config format prevents migration from legacy Syncthing app
Today I went to migrate from Syncthing to Syncthing-fork and found out that the import/export format was just changed. Oops! I had to install an older version of Syncthing-fork from F-Droid, import the config, and then update the app. Would it be possible…
Sto provando NVMe over Fabrics tra la zimaboard e il mio pc, figata spaziale. Si può esporre via TCP qualsiasi dispositivo a blocchi (sia dischi interi che partizioni, sia SSD che HDD, anche volumi LVM) con latenza zero e banda sfruttata al massimo.
Unico contro: anche se il protocollo supporta più client sullo stesso device, i dati verranno inevitabilmente corrotti, a meno di utilizzare un filesystem adatto per cluster
Unico contro: anche se il protocollo supporta più client sullo stesso device, i dati verranno inevitabilmente corrotti, a meno di utilizzare un filesystem adatto per cluster
🔥1
This media is not supported in your browser
VIEW IN TELEGRAM
Alternativa a ventoy ma via rete
https://www.netboot.xyz/docs
https://www.netboot.xyz/docs
🔥2