Programming N' LanguageRE: https://techhub.social/@pnl/116322249337262645
Read more in my blog post about this incident:
MrB33nEvery package you install runs code with your secrets in reach https://chat-to.dev/post?id=RVJvMkk0N1BiRU0yV3Y5NnRKOU1ZUT09&redirect=/profile?u=amargo85 #programming #hacker #websecurity #developers #technology
Every package you install runs code with your secrets in reach
Most devs don't think twice about `npm install` or `pip install`. But those commands can execute arbitrary code — before your app even starts. A malicious package doesn't need to exploit anything. It just needs to run during install, scan `process.env` for keys and tokens, and POST them somewhere. That's it. This isn't theoretical. In March 2026, Trivy's release pipeline was compromised. A malicious version hit PyPI and CI runners. LiteLLM got caught in the blast — two versions silently collected SSH keys, cloud credentials, Kubernetes tokens, and DB passwords from anyone who installed them. **The uncomfortable part:** most CI pipelines install packages in the same job that holds production secrets. One bad dependency, and it's all exposed. A few things worth doing: - Lock your dependencies (`package-lock.json`, `--require-hashes`) - Pin GitHub Actions to full commit SHAs, not `@v1` - Never let the install step see your runtime secrets - Watch outbound traffic from build environments Full breakdown here → https://www.eliranturgeman.com/2026/03/28/supply-chain-attacks/
🤪 Wake up at 6 to find the website under extreme stress. Spent an hour configuring rules on Cloudflare, the Under Attack mode saved the day! What a time to we are living in!
Are most traffic from AI bots these days?
LogicLuminaryBillSunday, March 22, 2026
Day 80 of Year 3
Day 811 overall since Jan 1, 2024
💻 nhcarrigan-mentorship:
• Strengthened backend fundamentals through consistent debugging
• Reviewed API route structure and request flow
• Improved familiarity with Express, Prisma, and database-backed development
Strong fundamentals build resilient systems. Keep refining, keep improving. ⚙️
#JavaScript #BackendDevelopment #WebSecurity #APIDevelopment #WebDevelopment #DevJourney #SoftwareEngineering #100DaysOfCode
Rubén Santos GarcíaOAuth account takeover doesn't need leaked tokens. No state param = CSRF to forced account linking. Loose redirect_uri matching = code theft via open redirect chains. Implicit flow puts tokens in browser history and Referer headers. PKCE bypass when not enforced server-side. SSRF via OpenID dynamic client registration. Six patterns, all with labs. https://www.kayssel.com/newsletter/issue-43/ #OAuth #BugBounty #Pentesting #websecurity #Offsec #InfoSec
Bug Bounty ShortsFrom Directory Listing to Breaking Logins
This article details a sequence of vulnerabilities chained together during a bug bounty engagement. The initial flaw was directory listing exposure due to misconfigured Apache server settings, causing the disclosure of sensitive files like password hashes. The researcher used tools like gobuster and dirbuster to discover hidden directories and subdirectories containing potentially sensitive data. Next, he leveraged a weak hashing algorithm (MD5) and rainbow tables to crack the exposed passwords. By exploiting multiple account takeover vulnerabilities, he gained access to various user accounts with administrative privileges. The attacker successfully exploited XSS via an injection payload ('<img src onerror=alert(document.cookie)>') in a login form and logged into an admin account without supplying valid credentials. This chain of flaws resulted in unauthorized access, data exposure, and account takeovers. The researcher received $10,000 for reporting the vulnerabilities. To remediate, apply strict permissions to sensitive files, use strong hashing algorithms, and sanitize user inputs to prevent XSS attacks. Key lesson: A single weakness can lead to a cascade of vulnerabilities; always address them promptly. #BugBounty #Cybersecurity #WebSecurity #DirectoryListing #PasswordHashing #XSS
I Spent 3 Months Failing at Bug Bounty — This Roadmap Fixed Everything
The article describes a bug bounty beginner's experience and the roadmap that helped him improve his skills. The root cause of his initial failures was lack of understanding about common web vulnerabilities (e.g., XSS, SQL Injection) and ineffective searching strategies. To exploit an XSS vulnerability on a test platform, he used payloads like '<img src=x onerror=alert(1)>'. The flaw here was insufficient input sanitization of user-supplied data, enabling arbitrary JavaScript execution within the application's context. By following a tailored learning path (e.g., reading books, attending workshops, joining communities), he enhanced his skills and went from zero to hero in bug bounties. The takeaway is that persistence, practice, and structured learning can help anyone succeed in bug bounties. #BugBounty #Cybersecurity #WebSecurity #XSS
Local File Inclusion in a PHP Reservation System — From Parameter Abuse to Source Code Disclosure
This vulnerability was a Local File Inclusion (LFI) in a PHP reservation system due to insufficient input validation on user-controlled parameters. The application failed to properly sanitize $_GET['page'] requests, allowing attackers to supply arbitrary file paths (e.g., '../config.php') for inclusion within the page content. By crafting payloads that leveraged this flaw, such as 'index.php?page=../../config.php', the researcher could access sensitive configuration details like database credentials and even view source code. The attack vector involved injecting the LFI payload into the 'page' parameter to trigger file inclusion from an unintended location outside of the intended directory structure. This flaw demonstrated poor sanitization of user-controlled parameters, leading to information disclosure and potential access control bypasses. The attacker received $5,000 for reporting the vulnerability. To remediate, validate user inputs carefully before processing them, especially when including files using functions like include() or require(). Key lesson: Always sanitize user-controlled parameters before file inclusion to prevent Local File Inclusion (LFI) attacks. #BugBounty #Cybersecurity #WebSecurity #InputSanitization #LocalFileInclusion
Cross-Site Scripting (XSS) Explained: How a “Low Severity” Vulnerability Leads to Enterprise Compromise
This vulnerability is an XSS (Cross-Site Scripting), which enables JavaScript execution via user input. The root cause lies in insufficient input sanitization of URL parameters by the application, allowing malicious scripts to be injected through a seemingly innocuous 'Enable JavaScript and cookies' prompt. The attacker utilized this flaw to craft payloads that stole session cookies and executed arbitrary client-side code within the context of the vulnerable website. The impact includes information disclosure, unauthorized account takeover, and potential data breaches. The researcher received a bounty (amount undisclosed) for reporting the vulnerability. To remediate, validate and sanitize all user inputs to prevent XSS attacks, ensuring they only contain safe characters. Key lesson: Never trust user-provided input blindly; always validate and sanitize it before rendering on the client side. #BugBounty #Cybersecurity #XSS #InputSanitization #WebSecurity
WIZ Bug Bounty Master Class: SSRF Vulnerability on Major Gaming Company
This vulnerability is an SSRF (Server Side Request Forgery) in a major gaming company's application. The root cause was the insufficient validation of user-controlled headers, such as 'Host', when making requests to internal services. By crafting payloads that leveraged this flaw, such as '<http://10.0.0.1> <http://internal.service>', the researcher could make outgoing requests from the application server to internal IP addresses (e.g., 10.0.0.1) and bypass network-level access controls. This allowed him to discover and enumerate sensitive data, like system configuration details, potentially leading to privilege escalation. The attacker received $5,000 for reporting the vulnerability. To remediate, validate IP addresses at the network layer, whitelist trusted hosts, and sanitize user-controlled headers. Key lesson: Validate requests made by application servers carefully to prevent SSRF attacks. #BugBounty #Cybersecurity #WebSecurity #SSRF
