Bug bounty Tips
Open in Telegram
🛡️ Cybersecurity enthusiast | 💻 Helping secure the digital world | 🌐 Web App Tester | 🕵️♂️ OSINT Specialist Admin: @laazy_hack3r
Show more7 582
Subscribers
+924 hours
+567 days
+29230 days
Posts Archive
7 582
🤑 Binance Back explained
On Thursday 29 October at 20:24 UTC, a single transaction on Ethereum sent 1.6 billion dollars in Tether, 167,464 ether and 62 other tokens from a Binance withdrawal wallet to an attacker. Three and a half minutes earlier, the attacker had taken control of that wallet with a permission carrying the wallet’s own signature, according to TRM Labs. Binance estimates the total impact at about $6.3 billion, across ten networks. In 2003, Saddam Hussein’s son had $1 billion in cash loaded onto three trucks. In $100 bills, Thursday’s sum would weigh about 63 tonnes. Tether blacklisted the attacker’s address 37 minutes after the transaction and froze 971 million Tether tokens. In Tether’s code, the address that function takes is named “_evilUser”. Circle froze 823 million USDC three minutes later. By 1 am UTC, Binance said about $3 billion had been frozen. Frozen is not returned: the attacker simply cannot spend it. Binance says it will cover all losses. Its first findings pointed to a compromised engineer’s laptop, and it has since reported additional points of breach. TRM Labs and Chainalysis attribute the attack to a North Korean hacking unit. Binance has not named anyone. The part no company can freeze: at 00:30 UTC, TRM counted more than 420,000 ether and 18,270 bitcoin still with the attacker, about $2.4 billion. The bitcoin sits in 19 wallets, and none of it had moved this morning. Some of the ether has. Sources: Binance (announcement and X posts), TRM Labs, Chainalysis, Tether, Circle, Arkham, CoinDesk, Decrypt, Cointelegraph, BBC, The Guardian, Ethereum and Bitcoin transaction records, Guinness World Records, US Bureau of Engraving and Printing. Checked 30 Oct, 12:30 CET. Narration: synthetic voice. Truck model: “[Riveria opettaa] Truck, Trailer and Forklift” by Jorma Rysky, CC BY 4.0 (Sketchfab), forklift removed. Cover: “Over $1,000,000 dollars in USD $100 bill stacks”, Flying Logos, CC BY-SA 4.0. #Binance #Crypto #Cybersecurity #NorthKorea #Bitcoin
7 582
#MLSecOps
#Cloud_Security
#Threat_Research
The Rise of LLMJacking: How Threat Actors Monetize Compromised Cloud and Model Resources
https://cloud.google.com/blog/topics/threat-intelligence/llmjacking-monetizing-compromised-cloud-models
]-> AWS Bedrock API keys security toolkit
]-> AgentDecoy
// The combination of TruffleHog (on CI/CD for checking secrets) + Portkey/AI gateway (as a single entry point for code, hiding keys) + LLMeter (for instant alerts) covers up to 95% of the risks of becoming a victim of LLMJacking.
7 582
#SCADA_Security
1⃣ How the PHP2Shell Vulnerabilities May Affect CPS Environments
https://blog.claroty.com/blog/how-the-php2shell-vulnerabilities-may-affect-cps-environments
2⃣ Exploitation Targeting Node-RED on Siemens SIMATIC IoT2050 (CVE-2026-58115)
https://www.vulncheck.com/blog/exploitation-targeting-node-red
7 582
#exploit
#Kernel_Security
Dangerous Device: Exploiting CVE-2026-31695
in the Linux Kernel via struct device
https://a13xp0p0v.github.io/2026/11/02/CVE-2026-31695.html
// Linux kernel race/UAF in network device management
// Disclaimer
7 582
#compilers
#MLSecOps
"CipherFlow: Compiling AI Programs for Efficient Cryptographically Secure Inference", 2026.
]-> https://loopleap-lab.github.io/CipherFlow
// CipherFlow takes a high-level AI computation graph, available cryptographic primitives, and a target hardware and network configuration to construct a latency-optimized hybrid secure inference plan
7 582
#Analytics
#Blockchain_Security
2026 H1 Global Web3 Security Report
// New critical threat - RPC Poisoning
See also:
]-> Q2 2026 Security & Compliance Report
7 582
#MLSecOps
MLSecOps Practical Reference Guide v.1.3.0
open-source handbook for AI security, machine learning security, and secure MLOps across the full ML lifecycle - from data and training through deployment, runtime monitoring, SOC, and governance
https://github.com/MHaghighian/MLSecOps/tree/v1.3.0
7 582
#AppSec
#NetSec
1⃣ CVE-2026-97631:
Pre-boot RCE in EDK II PXE driver
https://github.com/tianocore/edk2/security/advisories/GHSA-99cj-7hg9-mp4m
2⃣ Unauthenticated file read leaks master key on Enterprise proxy
https://github.com/BerriAI/litellm/security/advisories/GHSA-w4c7-34wj-hqm8
3⃣ XSS in Cloudflare's /cdn-cgi/image/
https://www.slcyber.io/research/cache-me-if-you-can-xss-in-cloudflares-cdn-cgi-image
7 582
#Kernel_Security
Infinity Core: Linux Kernel Core LPEs
https://github.com/V4bel/InfinityCore
// The vulns (CVE-2026-98260, CVE-2026-98256, CVE-2026-89754, CVE-2026-80775, CVE-2026-98385, CVE-2026-97941) covered here affect Kernel Core subsystems that have historically seen relatively few security issues. They enable LPE and container escape on Linux distributions, and some also allow an attacker to gain full root privileges from the Android untrusted_app domain
7 582
#MLSecOps
#Red_Team_Tactics
"GenAI Red Teaming Manual:
A Practical Guide for Adversarial Testing of Generative AI Models & Systems", Oct 2026.
// Its eight-phase methodology covers planning, reconnaissance, attack surface mapping, exploitation, persistence, impact assessment, reporting, and remediation. Addressing models, applications, multimodal interfaces, and AI agents, it emphasizes ethical testing, reproducible findings, measurable outcomes, and integration with defensive operations
7 582
#tools
#Fuzzing
#Sec_code_review
Fuzzers vs. AI: Comparing Fuzzilli and BigSleep
on JavaScript Engines
https://projectzero.google/2026/10/fuzzing-v-AI.html
7 582
#info
#tools
PHP2Shell: 22-27 October 2026
https://gist.github.com/0x4D31/6b1e7b5fb7a10219af187be91335c96f
]-> PHP RCE Vulnerabilities Exploited on Palo Alto Networks PAN-OS (CVE-2026-109618, CVE-2026-109619)
]-> High Fidelity Detection Mechanism
]-> Analytics Story
7 582
#DevOps
#Tech_book
"DevSecOps and DevOps for Linux:
The Foundations", 2026.
]-> https://github.com/Apress/DevSecOps-for-Linux
// This book focuses on the widest interpretation of DevSecOps, which blends security concepts into DevOps. For this reason, it illustrates not only concepts strictly related to DevSecOps, but also DevOps concepts since it is not correct to take them for granted
7 582
#tools
#MLSecOps
"The Trigger in the Haystack:
Extracting and Reconstructing LLM Backdoor Triggers", Feb. 2026.
]-> https://github.com/microsoft/llm-backdoor-scanner
