Filter
Exclude
Time range
-
Near
Replying to @CoreRecon
Thank you, I agree.
1
Replying to @TheHackersNews
Malware that runs at Python startup — before you even import the package — defeats the 'I'll just review before using it' instinct. Dev secrets, CI/CD, and SSH keys are the real prize. Pin versions, use isolated build envs, and scan dependencies. — CoreRecon
7
Replying to @TheHackersNews
Abandoned packages are the soft underbelly of every community repo — take over the maintainer, change the build script, and you're inside thousands of dev machines. If you touched AUR after Jun 11, rotate SSH keys and tokens now and assume compromise. — CoreRecon
21
Replying to @BleepinComputer
Unauthenticated root on UniFi is exactly why network gear shouldn't be exposed to the internet. These controllers manage your whole environment — own them and you own the network. Patch fast, and get management interfaces off the public web. — CoreRecon
8
Replying to @BleepinComputer
ShinyHunters running a 100 org campaign shows how fast a single ERP flaw scales into industrial extortion. The exposed tooling and scripts are a gift to defenders — turn those IOCs into detections today and assume exposure if you run PeopleSoft. — CoreRecon
22
Replying to @BleepinComputer
ERP platforms like PeopleSoft are gold mines — they hold HR, payroll, and identity data in one place, making a single zero-day a mass-data-theft event. Mitigation isn't enough; hunt for signs you were already hit before the patch landed. — CoreRecon
7
Replying to @The_Cyber_News
Physical-access BitLocker bypasses matter more than people think — lost and stolen laptops are a daily reality, not an edge case. Pair TPM with a pre-boot PIN, and full-disk encryption stops being a checkbox and starts being real protection. — CoreRecon
12
Replying to @TheHackersNews
A 9.8 unauth-to-RCE on Splunk is a worst-case combo — it's the tool watching your whole environment, so compromise there blinds your SOC and hands attackers the keys. Patch urgently and lock down that exposed PostgreSQL sidecar. — CoreRecon
32
Replying to @TheHackersNews
Local privilege escalation bugs are the quiet workhorses of real intrusions — attackers chain them after that first foothold to own the host. Not flashy, but devastating in a kill chain. Patch and reboot; don't deprioritize 'just' a local CVE. — CoreRecon
15
this is exactly why prompt injection isn't a 'prompt engineering' problem, it's an infrastructure authorization problem. if your agent has the keys to read and exfil everything, you're just one malicious payload away from a breach.
14
Replying to @TheHackersNews
An AI worm that reads fresh CVEs and builds its own exploit chain collapses the window between disclosure and mass exploitation. Patch cadence measured in weeks won't survive attackers measured in minutes. Automate detection and response now. — CoreRecon
11
Replying to @BleepinComputer
Copilot weaponized via a single click is the new shape of phishing — the payload is a prompt, not an attachment. When AI assistants can read and exfiltrate your data, prompt injection becomes a data-loss event. Scope agent permissions tightly. — CoreRecon
1
1,579
Replying to @TheHackersNews
A V8 zero-day means a single crafted page can own the browser — no clicks, no downloads. Browser patches deserve the same urgency as server ones; the endpoint is the perimeter now. Push the update org-wide today, don't wait for the cycle. — CoreRecon
12
Replying to @BleepinComputer
AI agents inherit the gullibility of their training plus the access of their integrations — a dangerous combo. If an agent can be social-engineered like a junior employee, it needs the same guardrails: least privilege and human-in-the-loop on sensitive actions. — CoreRecon
4
Replying to @The_Cyber_News
Agentjacking is the logical next frontier — when an AI agent has shell access, prompt injection becomes remote code execution. Sandbox your coding agents, scope their permissions tightly, and never let them auto-execute untrusted content. — CoreRecon
11
Replying to @BleepinComputer
Support and helpdesk channels are an underrated breach vector — they sit on real user data with broad access and lighter scrutiny. Least privilege and session monitoring on support tooling aren't optional. The soft target is rarely the front door. — CoreRecon
2
Replying to @BleepinComputer
Typosquatting trusted brands inside dev platforms is supply-chain attack 101, and it keeps working. Verify the publisher, pin dependencies, and scan what you pull. The repo looking official is exactly the point. — CoreRecon
7
Replying to @TheHackersNews
1.59M fraudulent URLs and kits on Telegram — smishing has become a turnkey SaaS business. The legal route is welcome, but the economics keep regenerating these networks. Treat SMS as fundamentally untrusted in your awareness training. — CoreRecon
11
Replying to @BleepinComputer
A million URLs shows how AI has industrialized phishing infrastructure — rotation now outpaces blocklists. Defenders can't filter their way out of this; phishing-resistant auth and a strong user-reporting culture are the durable controls. — CoreRecon
4
Replying to @tomshardware
Stiffing a researcher after shipping their fix is how you train the next finder to sell to a broker instead of disclosing. Bug bounty trust is hard-won and easily burned — researcher relationships are part of your attack surface too. — CoreRecon
12