Cybersecurity news aggregator
treemd <(curl -sL https://allsec.sh/md) (as Markdown) This week kept coming back to permission. A model crossed a boundary. A wallet trusted bad randomness. Webmail kept an intruder around. Public systems, package feeds, hotel networks, and login flows all gave away more than intended. Some of it was clever. Most of it was just access left lying around: old bugs, exposed gear, poisoned dependencies, weak defaults, and tooling that moved from
A credential-stealing npm worm that first appeared in keyv@6.0.0 spread beyond the Keyv and Cacheable namespaces into hundreds of packages across multiple organizations on August 4, 2026. SafeDep verified 353 poisoned versions across 79 package names in the npm registry. Its monitoring put the wider footprint at 442 versions across 353 names, while Aikido later reported at least 868 packages
Engineering managers spent the past few decades figuring out ways for many programmers to work together on a shared codebase. This work dates all the way back to the âSystems Development Lifecycleâ ( RAND, 1975 ) - today commonly referred to as the âSoftware Development Lifecycleâ (SDLC), which defines the following phases: Plan Design Implement Test Deploy Maintain Retire AI has made the step that was previously the slowest and most expensive â implementation â the fastest and cheapest. That, in turn, has had an impact downstream: overwhelming the people responsible for all the other steps in the SDLC. This ranges from open-source maintainers bombarded with thousands of pull requests and issues, to production engineers trying to save production from falling over as the rate of software delivery increases orders of magnitude. We are all trying to save our systems, our customers, and ourselves from slop. The answer â paradoxically â is to empower agents to do more. Itâs only fair! Youâd never let an engineer on your team write code, expect someone else to validate it, merge it, deploy it, hold the pager in production, and triage incoming bugs. But thatâs what most companies are doing right now with agents. Models have improved remarkably, and agents are running over longer time horizons, able to take on much larger tasks. But they are not yet used evenly across the SDLC. Cloudflare treats agents as our customers. They can buy domains , create temporary accounts and
Everyone is talking about software factories: the idea that AI agents can be assembled into a pipeline that produces working software on their own, the way a factory turns raw materials into finished goods. Thereâs endless debate over whether thatâs actually possible, how far the automation can really go, and whether the âloopsâ people are demoing count for anything. Some have already written them off as a failure. Running alongside that is a quieter, more worried conversation: open source maintainers are burning out. The AI boom has made it nearly free to generate issues, pull requests, and security reports, and enormously expensive for a maintainer to read through them all. The old ways of keeping a project healthy are buckling under the volume. Everyone has a hot take on both topics. We think we have something rarer to offer: real results. For the past several months weâve run an automated triage pipeline on the Astro repository. It reads incoming bug reports, reproduces them in sandboxes, diagnoses the root cause, and ships preview releases for the reporter to verify. The engine underneath it grew into Flue , an open framework for building this kind of agent automation, and itâs the same tool you could use to build your own. It wasnât an instant success. But through a lot of iteration, weâve used it to bring our open issues down from over 200 to about 30, and we expect to hit zero sometime in the next month. That would be the first time this repository has seen zero open issues in its 5+ year history. We didnât get there by declaring "issue bankruptcy," auto-closing cold tickets, or ignoring reports. We did it by automating issue triage with a team of isolated AI subagents running right inside GitHub Actions. Hereâs the story of how we got there, and what you might take back to your own projects. Sta
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday added a high-severity security flaw impacting N-able N-central to its Known Exploited Vulnerabilities (KEV) catalog following reports of active exploitation in the wild. The vulnerability, tracked as CVE-2026-18577 (CVSS score: 8.2), is a case of incomplete patching for CVE-2026-18556 (CVSS score: 8.2) that allows
EtherRAT off a The Gentlemen staging server. C2 resolution is the fun part: no hardcoded domains. The sample holds an Ethereum contract address + call selector and pulls the active C2 from the contract via public RPC endpoints. Every operator rotation is a contract write, so the full history is recoverable, five domains here. Tasking has no fixed command set. Any response over ten chars is thrown into a new async function with require, process, Buffer, etc. in scope, so arbitrary JS in the user context. Polls use random file-like paths (png/css/ico) to blend in, tell is a custom X-Bot-Server header. MSI drops a Node bootstrapper + XOR-encrypted backdoor, decoder writes plaintext and sets a Run key relaunching via headless conhost. Full write-up with hashes and IOCs: [https://hunt.io/blog/the-gentlemen-etherrat-ethereum-smart-contract-c2](https://hunt.io/blog/the-gentlemen-etherrat-ethereum-smart-contract-c2)
Now, it is possible to query phishing-suspect FQDNs through the free API, featuring database information on WHOIS, IP, Geolocation, and threat mapping [https://github.com/julioliraup/AT/wiki/REST-API-USE](https://github.com/julioliraup/AT/wiki/REST-API-USE) A frontend interface is also available: [https://julioliraup.github.io/AT](https://julioliraup.github.io/AT)
The commercial phishing-as-a-service (PhaaS) toolkit known as Greatness has become the latest crimeware solution to add support for device code phishing, a rapidly growing cyber threat that abuses the legitimate OAuth 2.0 Device Authorization Grant to bypass Multi-Factor Authentication (MFA) and seize control of user accounts. "Greatness supports AiTM [adversary-in-the-middle] credential and
Facing a growing drone threat, the Pentagon is poised to sign a first-of-its-kind contract for âEnduring High Energy Lasersââand make directed energy weapons an official part of the Armyâs kit.
Disclosure: I write a daily security newsletter, this was today's issue. The substance is below, link at the end. Thermo Fisher's July 31 bulletin covers CVE-2026-17583 (CVSS v4.0 8.2). The .fsa and .hid files from Applied Biosystems human identification instruments can be modified between the instrument writing them and the analysis software loading them, and the change is nearly undetectable. Nothing in the file let the software confirm the bytes were the ones the instrument wrote. Nathan Adams of Forensic Bioinformatics told the WSJ his first successful modification took about 45 minutes, merging scans from two DNA profiles into one file that presented as untouched since 2015. The updates add digital signatures, which only protects files written after the upgrade. The bulletin does not address retroactive validation, the researchers found no way to detect prior tampering, and these file types have been produced since 1995. Three end-of-life product lines get no update at all. Full writeup with the affected versions and remediation order: [https://www.linkedin.com/pulse/researchers-altered-dna-evidence-file-45-minutes-tymoteusz-netter-bxhhf/](https://www.linkedin.com/pulse/researchers-altered-dna-evidence-file-45-minutes-tymoteusz-netter-bxhhf/) Bulletin: [https://documents.thermofisher.com/TFS-Assets/CORP/Product-Guides/fsa\_hid\_bulletin.pdf](https://documents.thermofisher.com/TFS-Assets/CORP/Product-Guides/fsa_hid_bulletin.pdf) Most of us have outputs a downstream process treats as authoritative without checking provenance. For files predating any signing mechanism, write-access logs on the landing directory are the only retrospective evidence I can build. What are you using?
- [ChainDrop npm Worm: Bun-loaded CI/CD credential harvester with Ethereum dead-drop C2](https://www.stepsecurity.io/blog/chaindrop-npm-worm) - [Popular npm Packages in the keyv and Cacheable Namespaces Compromised in Active Supply Chain Attack](https://socket.dev/blog/popular-npm-packages-in-the-keyv-and-cacheable-namespaces-compromised-in-active-supply-chain) - [npm Worm Poisons 400+ Packages Across Nine Organisations](https://safedep.io/keyv-npm-supply-chain-compromise/)
Hey, A few years ago I made this website that can download and inspect chrome extension in memory (extraction, not execution), so that you don't have to download or view them in an editor. There are some similar tools out there, but I made this one for my self when I needed to review browser extensions. I ended up adding features I needed, such as searching across all files. I will never add any ads or 3rd party stuff to this site so feel free to use it. [https://showmecode.dev/](https://showmecode.dev/) other features are: \- beautifies minified code (this can be toggleable in the settings) \- download zip/crx \- shareable URLs to the specific extension + file you are viewing \- supports chrome webstore, firefox and edge store
A credential-stealing npm worm that first appeared in keyv@6.0.0 spread beyond the Keyv and Cacheable namespaces into hundreds of packages across multiple organizations on August 4, 2026. SafeDep verified 353 poisoned versions across 79 package names in the npm registry. Its monitoring put the wider footprint at 442 versions across 353 names, while Aikido later reported at least 868 packages
Our team has just published new research about exploiting Zero Touch Provisioning (ZTP), specifically targeting TP-Link's Omada ecosystem: [https://www.forescout.com/research-labs/zero-touch-provisioning-is-a-fleet-scale-attack-vector/](https://www.forescout.com/research-labs/zero-touch-provisioning-is-a-fleet-scale-attack-vector/) The research discloses 15 new vulnerabilities and some extend beyond Omada into other TP-link product lines. What led us to do this research was the fact that we see many attacks against edge devices exploiting remote code execution for individual assets, but we wondered if there were additional flaws that could extend to a whole ecosystem of devices. The vulnerabilities have been fixed by TP-link and the research will be presented at Black Hat and DEF CON this week: [https://blackhat.com/us-26/briefings/schedule/index.html#zero-day-provisioning-chaining-tp-link-ztp-vulnerabilities-for-infiltrating-networks-51879](https://blackhat.com/us-26/briefings/schedule/index.html#zero-day-provisioning-chaining-tp-link-ztp-vulnerabilities-for-infiltrating-networks-51879) Please stop by if you are attending either conference and let us know if you have any questions about this research.
Cybersecurity researchers have disclosed details of an active, multi-wave campaign that employs social engineering lures themed around Adobe and Zoom software updates, business document reviews, and system maintenance utilities to stealthily deploy Remote Monitoring and Management (RMM) programs like ConnectWise ScreenConnect. The campaign has been codenamed SMOKE#SCREEN by Securonix Threat
Engineering managers spent the past few decades figuring out ways for many programmers to work together on a shared codebase. This work dates all the way back to the âSystems Development Lifecycleâ ( RAND, 1975 ) - today commonly referred to as the âSoftware Development Lifecycleâ (SDLC), which defines the following phases: Plan Design Implement Test Deploy Maintain Retire AI has made the step that was previously the slowest and most expensive â implementation â the fastest and cheapest. That, in turn, has had an impact downstream: overwhelming the people responsible for all the other steps in the SDLC. This ranges from open-source maintainers bombarded with thousands of pull requests and issues, to production engineers trying to save production from falling over as the rate of software delivery increases orders of magnitude. We are all trying to save our systems, our customers, and ourselves from slop. The answer â paradoxically â is to empower agents to do more. Itâs only fair! Youâd never let an engineer on your team write code, expect someone else to validate it, merge it, deploy it, hold the pager in production, and triage incoming bugs. But thatâs what most companies are doing right now with agents. Models have improved remarkably, and agents are running over longer time horizons, able to take on much larger tasks. But they are not yet used evenly across the SDLC. Cloudflare treats agents as our customers. They can buy domains , create temporary accounts and
Today, it is difficult for AI agents to try out new APIs. They often have to navigate through a login page designed for humans and not agents, contact a human to add a payment method, generate an API key, and then figure out how to call the API. This flow is very difficult for agents for two reasons: Agents do not have a stable identifier to sign up for an API, and they do not have a native way to pay for APIs. Because they lack these things, they often struggle to onboard onto software, which limits the growth of agentic commerce. AI agents often give up on these tasks entirely, kicking registration, payment methods, and API key generation back to humans. This makes it very difficult for agents to try out and compare many APIs. To solve this, weâve created Cloudflare Wallets. Starting today, you can claim a Cloudflare Wallet handle for your account, which will provide a unique username to help you better connect with merchants. Soon, you will be able to set up and use your Cloudflare Wallet to pay for APIs and content. Earlier this month, we announced the Monetization Gateway to help Cloudflare customers get paid for their websites and applications. Monetization Gateway will support micropayments using the x402 protocol , which allows for payments to be attached to HTTP requests. These micropayments will be able to pay for uses ranging from AI inference to data to content. If you want to pay or get paid for services behind Monetization Gateway and other x402-compatible endpoints , youâll need a wallet. Cloudflare Wallets will allow you to store s
We are moving toward a world in which you can store, build, test, and deploy your code fully on Cloudflare. We built the first piece with Artifacts , versioned code storage that scales to millions of repos. We have stitched the store, build, and deploy steps together with the CI SDK , built on Cloudflare Workflows , so that you can run your continuous integration (CI) pipeline on Cloudflare. You can send artifact push events directly to your Workflow, triggering an instance of its execution â a CI job, essentially â through a new events field in your wrangler configuration file. Then, directly from the Workflow with @cloudflare/ci installed, you can: Automate builds: compile code from your Artifacts repo in a safe, isolated environment Run linters and typechecks: enforce code style, catch type errors, and flag any potential issues Cache dependencies: run your install once and cache dependencies across steps in the CI job Execute unit tests: verify that each piece of your code works as expected Self-heal: integrate an AI review agent to catch broken steps in your build and push commits to fix Deploy conditionally: automatically deploy your code, only if your build step is successful Today, everyone is building a platform, whether itâs an internal vibe coding platform or an extension of your customer-facing product via customization through code.
Over the past four months, our AI code reviewer has flagged nearly a quarter of a million deviations from Cloudflare engineering standards (what weâll call âviolationsâ in this post) and blocked 16,000 merges. Our spec reviewer agent has evaluated close to 600 technical designs against the same standards before implementation began. Both systems draw from the Cloudflare Codex, a shared source of engineering guidance built for people and agents. This post explains why we built the Codex, how it supports the engineering lifecycle, and what we plan to do next. Before the Codex (which we briefly introduced in a previous post about our AI engineering stack), developer guidance at Cloudflare lived in many places: formal documentation, repository files, chat threads, and the accumulated knowledge of individual engineers. Engineers often spent too much time searching for guidance instead of working on the problem they were trying to solve. Even after finding an answer, they could not always tell whether it was current, authoritative, or applicable to their situation. As Cloudflare grew, that model became increasingly difficult to sustain. No engineer could read every standard, and reviewers could not reliably check every requirement. Institutional knowledge became harder to recover when people moved between teams, and guidance that was not consistently surfaced or enforced led to drift between projects. We rebuilt this body of knowledge as the Cloudflare Codex: a governed set of engineering standards that agents can retrieve and apply at the point of work. The same guidance can now inform code review, technical design review, incident report review, and many other use cases, while engineers focus their time and judgment on the resul
Starting today, wrangler dev and vite dev automatically capture OpenTelemetry traces for local Worker invocations. When Cloudflare's tooling detects an agent session, it points the agent to the Local Explorer API , a local debugging API where it can query those traces. You do not need to install an SDK, enable tracing, configure your agent, or even mention observability in the prompt. A prompt can be as simple as: This builds on years of investment in local development, from introducing Miniflare to making local mode the default in Wrangler 3 . Local traces give coding agents structured feedback from that development environment before code is deployed. Agents discover the Local Explorer API automatically As part of its normal workflow, an agent starts wrangler dev or vite dev to run and test the Worker. When the development server recognizes a supported coding-agent session, it automatically prints a hint that looks like this: The Local Explorer is a browser-based interface and REST API for viewing and editing local resource data and querying observability data during development. The API root serves an OpenAPI schema, so agents can discover available endpoint
Everyone is talking about software factories: the idea that AI agents can be assembled into a pipeline that produces working software on their own, the way a factory turns raw materials into finished goods. Thereâs endless debate over whether thatâs actually possible, how far the automation can really go, and whether the âloopsâ people are demoing count for anything. Some have already written them off as a failure. Running alongside that is a quieter, more worried conversation: open source maintainers are burning out. The AI boom has made it nearly free to generate issues, pull requests, and security reports, and enormously expensive for a maintainer to read through them all. The old ways of keeping a project healthy are buckling under the volume. Everyone has a hot take on both topics. We think we have something rarer to offer: real results. For the past several months weâve run an automated triage pipeline on the Astro repository. It reads incoming bug reports, reproduces them in sandboxes, diagnoses the root cause, and ships preview releases for the reporter to verify. The engine underneath it grew into Flue , an open framework for building this kind of agent automation, and itâs the same tool you could use to build your own. It wasnât an instant success. But through a lot of iteration, weâve used it to bring our open issues down from over 200 to about 30, and we expect to hit zero sometime in the next month. That would be the first time this repository has seen zero open issues in its 5+ year history. We didnât get there by declaring "issue bankruptcy," auto-closing cold tickets, or ignoring reports. We did it by automating issue triage with a team of isolated AI subagents running right inside GitHub Actions. Hereâs the story of how we got there, and what you might take back to your own projects. Sta
The cybersecurity industry has spent decades assuming that offensive capability scales with technical expertise. That assumption is starting to break. Security teams have long estimated risk by ranking attacker sophistication. Nation-state actors sat at one end. Organized criminal groups followed. Inexperienced attackers, dismissed as "script kiddies," sat at the other end, running public
cPanel has patched a flaw that let an authenticated hosting customer execute SQL in the database's root context, crossing the privilege boundary between a cPanel account and the server's administrative database identity. It shipped in a targeted security release that closes two other routes past account boundaries. The database bug is tracked as CVE-2026-58048 (CVSS 4.0 score: 9.4) and affects
A new Russian loader-as-a-service (LaaS) codenamed DOUBLECUP has been using ClickFix lures as a way to stage malware-laced PNG images in victims' browser cache and ultimately deliver CountLoader and a previously undocumented remote access trojan called DeviceManager. "The first stage drops a steganographic PNG image into the browser's cache, retrieves its hidden content, and executes the second
# Fake mParivahan : Malware Analysis Report # 422 Users are affected by it till now ( I was able to get the attackers admin panel ) **Classification:** Critical : Android SMS / UPI spyware RAT **Method:** Static reverse engineering of dropper + payload; no-root payload extraction; StringFog decryption; read-only Firebase C2 IOC enumeration # 1. Executive summary Marketed as **âM Parivahanâ** is a **two-stage Android malware** operation: 1. **Dropper** (`com.ioaheishsbsb.ljgcdfhm`) : NP Managerâpacked installer with a fake VPN / WebView UI that decrypts and sideloads an embedded APK (`output.apk`). 2. **Payload** (`com.veaheishsbsb.kekskks`) : Sketchware-style SMS/call spyware with **Firebase Realtime Database** command-and-control and **Telegram** first-run alerts. The payload steals SMS and device telemetry, can forward SMS and calls, and can send SMS from the victimâs SIM (commonly abused for UPI / OTP fraud). At the time of analysis the Firebase panel was r**everse engineered too** and contained **422** client device IDs. # 2. Sample identification |Field|Stage 1 (Dropper)|Stage 2 (Payload)| |:-|:-|:-| |Package|`com.ioaheishsbsb.ljgcdfhm`|`com.veaheishsbsb.kekskks`| |Related / alias|`com.mr_fox.bhai`|Label: âM Parivahanâ| |Application class|NP Manager shell|`np.protect.assets.ShellApplication`| |Protection|NP Manager (`libnp_protect_res.so`, xhook)|NP Manager + StringFog XOR| |UI|Fake VPN + `file:///android_asset/main_ui.html`|Permission / settings-style UX| |Embedded artifact|Logical asset `output.apk` (encrypted on disk)|â| |SDK|â|minSdk 21, targetSdk 28, compileSdk 33| |Build leftover|â|Synthetic names: `dApp-binance-Trading-Signals`| **Related package queried by dropper:** [`com.avejfhdhd.android`](http://com.avejfhdhd.android) # 3. Infection chain Victim sideloads fake âmParivahanâ APK â âź Dropper (NP Manager) decrypts embedded payload â âź Writes temp_info.apk / temp_install.apk â installs com.veaheishsbsb.kekskks â âź Payload requests SMS / phone permissions â âź MyService enrolls device on Firebase + dumps ~50 SMS â âź Telegram alert to operator bot/chat â âź Listens on clients/<deviceId>/webhookEvent for remote commands **Extraction note:** Static decrypt of the packed dropper blob failed due to native crypto. Payload was recovered without device root by patching the unpack path to `getExternalFilesDir` and pulling `/sdcard/Android/data/com.ioaheishsbsb.ljgcdfhm/files/temp_info.apk`. # 4. Capabilities |Capability|Severity|Detail| |:-|:-|:-| |SMS theft|Critical|Intercepts inbound/outbound SMS; uploads to `messages/<deviceId>`| |SMS forward|Critical|Relays SMS to operator number (`SmsForwardTo`)| |Remote SMS send|Critical|Sends SMS from chosen SIM (`sendSms` webhook)| |Call forwarding|High|USSD `**21*<number>#` / `##21#`| |Device fingerprinting|High|Model, Android version, root, storage, CPU, carrier, public IP, SIMs, battery, MSISDN| |Telegram notify|High|First-run HTML report to admin bot/chat| |Persistence|High|Foreground service, boot/alarm receivers, restart in `onDestroy`| |Keylogger flag|Medium|`KeyLogger` webhook present; appears stubbed/partial| # 5. Remote command surface **Listener path:** `clients/<androidId>/webhookEvent/` |Command key|Fields|Action| |:-|:-|:-| |`callForward`|`from`, `to`, `isActive`|Activate/deactivate call forward via USSD| |`smsForward`|`from`, `to`, `isActive`|Toggle SMS forward preference| |`sendSms`|`from`, `to`, `message`, `isSended`|Send SMS from victim SIM| |`checkLiveness`|`text=ping`|Reply `pong` under webhook| |`KeyLogger`|`isActive`|Preference flag (partial implementation)| Presence uses `clients/<id>/status` with Firebase `.info/connected` \+ `onDisconnect`. # 6. C2 infrastructure & IOCs # 6.1 Firebase |Item|Value| |:-|:-| |RTDB URL|`REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP`| |API key|`REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP`| |App ID|`REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP`| |Storage|`REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP`| |Top-level nodes|`clients`, `messages`, `devices`, `deviceMessages`| |Clients observed|**422** (2026-08-04, shallow enumeration)| |Rules posture|Open / world-readable (IOC check succeeded without auth)| # 6.2 Firebase path map |Path|Purpose| |:-|:-| |`clients/<androidId>`|Device profile enrollment| |`clients/<androidId>/status`|Online/offline| |`clients/<androidId>/webhookEvent/*`|Command inbox| |`messages/<androidId>/<timestamp>`|Stolen SMS| |`.info/connected`|Connectivity watch| # 6.3 Telegram |Item|Value| |:-|:-| |Endpoint|`https://api.telegram.org/bot<token>/sendMessage`| |Bot token|`REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP`| |Admin chat ID|`REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP`| |Config source|Raw resource `Loda` (obfuscated APK path `ŰŚ/ŰĽŰ`)| { "chatIDs": ["REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP"], "tokens": ["REMOVED I HAVE IT, IF ANY OFFICAL IS READING IT, PLEASE REACH OUT ASAP"], "workSuccess": 1 } Only **one** admin chat/token pair is embedded in the sample. # 7. Attacker / mule phone numbers **Not hardcoded in the APK.** Numbers are pushed via Firebase webhooks at runtime. From live `clients/*/webhookEvent` (`smsForward` / `sendSms` `to` fields), 2026-08-04: |Number|Hits|Observed role| |:-|:-|:-| |**8789**\*\*\*\*\*|**6**|**Primary SMS forward target (strongest IOC)**| |9279\*\*\*\*\*\*\*\*\*|2|SMS forward + sendSms| |8340\*\*\*\*\*\*\*\*\*|2|SMS forward| |9522\*\*\*\*\*\*\*\*\*|2|sendSms| |9279\*\*\*\*\*\*\*\*\*|1|sendSms (same line as 927\*\*\*\*\*\*\*\*\* with country code)| |8712\*\*\*\*\*\*\*\*\*|1 each|sendSms / UPI-style collect| |9211\*\*\*\*\*\*\*\*\*|1 each|sendSms / UPI-style collect| |8291\*\*\*\*\*\*\*\*\*|1|sendSms / UPI-style collect| |Others (one-offs)|1|Mixed sendSms destinations| **Primary SMS-intercept candidate:** `8789`\*\*\*\*\*\*\*\*\* UPI collect destinations may be money-mule wallets rather than the panel operatorâs personal line. # 8. Persistence & stealth # Components (payload) * Activities: `MainActivity`, `PermissionRequestActivity`, `DebugActivity` * Service: `MyService` (foreground; `FOREGROUND_SERVICE_MEDIA_PLAYBACK`) * Receivers: `SmsReceiver`, `BootReceiver`, `AlarmReceiver`, `MultiEventReceiver`, `BatteryLevelReceiver` * Persistent notification text: **âSystem Settings is RunningâŚâ** # Obfuscation / hardening * NP Manager resource and path mangling * StringFog (Base64 + XOR with key `UTF-8`) * Dropper encrypted asset (non-standard ZIP compression) * `usesCleartextTraffic="true"`, `allowBackup="true"` # 9. Dangerous permissions (payload) * `INTERNET`, `ACCESS_NETWORK_STATE`, `ACCESS_WIFI_STATE`, `CHANGE_*` * `READ_SMS`, `RECEIVE_SMS`, `SEND_SMS`, `DELETE_SMS`, `BROADCAST_SMS` * `CALL_PHONE`, `READ_PHONE_STATE`, `READ_PHONE_NUMBERS` * `RECEIVE_BOOT_COMPLETED`, `WAKE_LOCK` * `FOREGROUND_SERVICE`, `FOREGROUND_SERVICE_MEDIA_PLAYBACK` * `REQUEST_IGNORE_BATTERY_OPTIMIZATIONS`, `POST_NOTIFICATIONS` # 10. Key payload classes |Class|Role| |:-|:-| |`MyService`|Core RAT: enroll, listen, process commands| |`SmsReceiver`|SMS intercept / forward / Firebase write| |`TelegramBotUtils`|HTTP Telegram `sendMessage`| |`AdminInfo`|Load bot token â chat ID map| |`callForwardingUtility`|USSD call forward| |`SmsHelper` / `SMSRetriever`|Send SMS / dump inbox| |`DeviceInfoUtil` / `SimInfoUtil`|Fingerprint + public IP| |`SharedPrefManager`|`isFirst`, `isSmsForward`, `SmsForwardTo`, flags| |`BootReceiver` / `AlarmReceiver`|Keep-alive| # 11. MITRE ATT&CK (Mobile) mapping |ID|Technique|Evidence| |:-|:-|:-| |T1660|Phishing / fake app|mParivahan brand abuse| |T1406|Obfuscated files or information|NP Manager + StringFog| |T1624|Event triggered execution|`BOOT_COMPLETED`, `SMS_RECEIVED`| |T1517|Access notifications / SMS|SMS permissions + receivers| |T1437|Application layer protocol|Firebase + Telegram HTTPS| |T1636|Protected user data|SMS, MSISDN, SIM info| |T1428|Exploit via SMS / USSD|`sendSms`, `**21*`| |T1409|Stored application data|SharedPreferences C2 flags| |T1625|Hijack execution flow / packer|`ShellApplication` dropper|
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday added a high-severity security flaw impacting N-able N-central to its Known Exploited Vulnerabilities (KEV) catalog following reports of active exploitation in the wild. The vulnerability, tracked as CVE-2026-18577 (CVSS score: 8.2), is a case of incomplete patching for CVE-2026-18556 (CVSS score: 8.2) that allows
Intro In 2024 I released the initial version of Pipeleek. At the time the tool was a simple GitLab CI/CD pipeline secrets scanner, not much more. Since then, it has evolved quite a bit: Iâve added support for new CI/CD platforms, integrated the Renovate security research published last year, and built a range of helper commands on top of the scanner. Today itâs time to release version 1.0 of Pipeleek! Features Secret Scanner Platform Additions At its core Pipeleek is still a secrets scanner for exposed credentials in CI/CD pipelines. While many products scan for secrets at the version control level, Pipeleek covers leaked credentials in pipeline logs and artifacts. With version 1, Pipeleek supports the following CI/CD platforms: GitLab GitHub Bitbucket Azure DevOps Gitea CircleCI Jenkins Pentest Helpers
Cybersecurity researchers have discovered a new set of malicious npm packages that target users of Alibaba developer tools with a cross-platform remote access trojan (RAT) as part of a sophisticated, targeted software supply chain attack targeting Chinese-speaking environments. One of the packages in question is "lib-mtop," an unscoped package with the same name as a private Alibaba package
Malware running as an ordinary user on a Windows machine can sign into a victim's passkey-protected accounts without a fingerprint, a PIN, or anything at all appearing on the victim's screen. Unit 42 detailed three attack paths against Chrome's Google Password Manager cloud authenticator, which it calls Pass-ta-key, Silver Pass-ta-key and Golden Pass-ta-key; the strongest targets the master key
The INC Ransomware operation has emerged as the "dominant threat actor" exploiting the recently disclosed security flaws in SonicWall Secure Mobile Access (SMA) 1000 series VPN appliances. In a report published over the weekend, Resecurity said it observed the INC Ransomware accelerating its activity since the beginning of August 2026, listing multiple victims on its data leak site. Per
This week kept coming back to permission. A model crossed a boundary. A wallet trusted bad randomness. Webmail kept an intruder around. Public systems, package feeds, hotel networks, and login flows all gave away more than intended. Some of it was clever. Most of it was just access left lying around: old bugs, exposed gear, poisoned dependencies, weak defaults, and tooling that moved from
The most capable agents have something simple in common: they are given their own computer to work with. Coding agents work this way. You give them a filesystem, a shell, tools, packages, and the ability to run code. They inspect the environment, make changes, test their work, and keep going. The computer gives the model a familiar way to act on the world. At Cloudflare, weâre working hard to provide the right primitives on which to build the most capable agents. Today weâre introducing an early preview of @cloudflare/computer . The @cloudflare/computer package provides an agent runtime where the details and mechanics of what code runs in an isolate, a container sandbox, or a web browser are handled by the platform. Each agent gets a computer, the runtime optimizes for efficiency, and scalability. We believe that in order to meet the growing demand for compute required by agentic systems we need to look to solutions beyond traditional containerization. Changing how agents are built Weâve seen a subtle evolution of this story over the past six months. At the start of the year, spinning up a container and running an agent inside of it was the norm. In recent months, weâve seen a rapid move for agent harnesses to provide sandboxed code execution via tools. This separates the hands (the sandbox where work is done) from the brain (the agent loop). No matter where the harness runs, giving every agent a container presents a challenge â across all the clouds, all the hyperscalers, thereâs nowhere near enough compute in the world for every company to give each of their usersâ agents their own containerized compute environment. This will not scale to hundreds of millions, then billions, of concurrent agents. This is why there is desperate, panicked industry demand for CPU compute, not j
AI is changing how people interact with computers, and voice is becoming an increasingly important part of that shift. Real-time assistants, AI-powered dictation, and other voice interfaces need low-latency communication between clients, models, and supporting services. Many developers use gRPC , a Remote Procedure Call (RPC) framework built on HTTP/2 and TCP, for this infrastructure. Ever since Workers launched in 2017 , weâve been expanding their capabilities, including adding the ability to open outbound TCP connections and a JavaScript-native RPC system built on Capân Proto . And so as part of Agents Week, weâre extending Workers in the other direction, supporting inbound TCP connections and adding new ways to run gRPC applications on Cloudflare. Today, weâre announcing: connect(socket) â a new handler in the Workers runtime that lets your Worker directly accept an inbound TCP socket provided by Spectrum (Cloudflareâs ingress proxy for non-HTTP traffic) Full-duplex, bi-directional gRPC from Cloudflare Containers â forward the socket from your Worker to your gRPC server running in a container Workers can serve unary and server-streaming
Agents Week is about the shift already underway: agents write code, deploy Workers, and provision infrastructure on your behalf. That shift changes what you need to see. If a program is spending money in your Cloudflare account, you need to know what it's spending; throughout the day, per product, in a shape another program can consume. The dashboard is the right answer for humans. It's not the right answer for automation. So we're launching a new Billable Usage API for self-serve accounts: a single endpoint that returns your account's usage and cost, broken down by product and by service period. It covers every usage-based Cloudflare product on the account, including Workers, R2, D1, Workers AI, Vectorize, Images, and Stream, all with one call. And if you already work in a FinOps toolchain, the column names should look familiar. You'll get back an HTTP 200 OK with Content-Type: application / json and the usage rows in the response body. Today, usage and cost data are updated daily while we work towards providing more real time data. What comes back Each row in the response is one charge period for one product on your account. ServiceName and ServiceFamilyName â which product ("Workers Standard" under the "Workers" family, "R2 Storage" under "R2", etc.). ChargePeriodStart / ChargePeriodEnd â the window this row covers. PricingQuantity and ConsumedUnit â how much you used, in the unit of measure we bill on (GB-months, GB-seconds, requests, etc.). ContractedCost â what that period cost, in BillingCurrency . CumulatedPricingQuantity and CumulatedContractedCost â running totals for the billin
Workers AI runs inference for some of the best open models in the world on GPUs in Cloudflare data centers close to your users. Two of the most capable, and most demanding, are Moonshot's Kimi K-series and Z.ai 's GLM. They are large, long-context, mixture-of-experts models, and they are wonderful to use. They are also very hard to serve efficiently because of memory constraints. We've written before about how we serve large models on Workers AI and about separating the prefill and decode phases of inference to get more out of each GPU. This post looks at three techniques we layer on top of that to fit these models into memory and keep them fast: quantizing the KV cache, compressing the model weights, and, because both of those pack more requests onto shared hardware, protecting the cache those requests share. These optimizations enable us to support more customers at lower costs, with no change in model accuracy. All our experiments and production traffic are running and benchmarked with SGLang , an open-source inference serving framework. We found that SGLang offers the best performance in the market, and we work closely with the SGLang team to upstream patches and new features to make our work available to the open-source community. Quantizing the KV cache As a model generates text, it stores the attention keys (K) and values (V) for every token it has already processed in a structure called the KV cache. The cache is what lets the model extend a long conversation without re-reading the entire context on every new token. For a long-context model, it grows quickly, and it is usu
Two years ago, we introduced Workers RPC , built on Capân Proto RPC . This made it possible for Workers to call other Workers and Durable Objectsâ methods, return live objects and call their methods, return functions, streams and get all the benefits of a Remote Procedure Call (RPC) system, without defining schemas or adding any dependencies. We called it âJavaScript-native RPCâ because it made using RPC feel native to the language. Last year, we made this work between web browsers and servers, and introduced Capân Web . Now weâre taking it cross-language. Normally, getting programs written in different languages to talk to each other is complicated: developers usually have to build custom APIs or adopt language-agnostic serialization formats like protobuf , so the two systems can understand each other. The RPC system built into Workers is able to translate across JavaScript and Python without any additional work. You can now call methods defined in a Python Worker from a JavaScript Worker and vice versa. You can share objects across Python and JavaScript, and call methods on a Python object from TypeScript. It all just works. If you define a method add() in a Worker written in TypeScript: âŚyou can simply call it from Python: There are no dependencies needed. All you need to configure is a Service binding :
AI is moving incredibly fast, and every security leader is feeling the pressure to keep up. AI platforms like Claude, Codex and Cursor are already helping security teams write detections, investigate alerts, summarize incidents, and automate repetitive work. The conversation has evolved from whether AI belongs in the SOC, to where each type of AI delivers the most value. With so many new AI
An unknown Chinese-speaking threat actor has been observed running a campaign targeting Apple iOS devices by leveraging a publicly leaked version of the DarkSword exploit kit. Attack surface management platform Censys said it identified the threat actor running more than 100 web properties, most of which are fake Amazon Web Services (AWS) sign-in pages on a domain that also hosts the exploit
The Police National Legal Database (PNLD) has confirmed that police, government and customer contact information was compromised and published on the dark web. The data included names, organisations and work email addresses belonging to police officers, police staff, criminal justice professionals, government partners and customers. The incident, identified on July 26, also exposed some names
To reduce the amount of noise from questions, we have disabled self-posts in favor of a unified questions thread every week. Feel free to ask any question about reverse engineering here. If your question is about how to use a specific tool, or is specific to some particular target, you will have better luck on the [Reverse Engineering StackExchange](http://reverseengineering.stackexchange.com/). See also /r/AskReverseEngineering.
Three high-severity security flaws have been disclosed in Hugging Face's Diffusers library that could allow crafted model repositories to stealthily execute arbitrary code on machines that load it, opening the artificial intelligence (AI) supply chain to security risk. "These vulnerabilities are bypassing trust_remote_code, the safeguard designed to stop unreviewed code from running in the
Presently sponsored by: Report URI: Guarding you from rogue JavaScript! Donât get pwned; get real-time alerts & prevent breaches #SecureYourSite Today, we welcome the 47th government onboarded to Have I Been Pwnedâs free gov service: Nepal. Their National Cyber Security Centre now has access to monitor Nepalese government domains against the data in HIBP. This gives the NCSC the ability to identify exposure across government email addresses and respond quickly when those accounts appear in a new data breach. This is precisely what the HIBP government service was built for: helping national cyber teams strengthen threat monitoring and incident response capabilities by providing visibility into compromised credentials and breached accounts across their government domain space. Nepal joins a growing list of governments and national cybersecurity teams using HIBP to better understand their exposure, protect government departments and public resources, and reduce the risk posed by compromised credentials before attackers can take advantage.
Presently sponsored by: Report URI: Guarding you from rogue JavaScript! Donât get pwned; get real-time alerts & prevent breaches #SecureYourSite Apparently, Aussies are so obsessed with coffee that it's referred to as the coffee capital of the world down here (some bits, at least). "But what about Italy?" people ask. Having spent a lot of time in a lot of Italy, no, it's just not the same. It's not the same ubiquity of high-quality coffee shops and passion for what many view as the art of making espresso-based drinks. There's comparably little tolerance for the likes of Starbucks ( who have not fared well in Australia ), and other mass-produced forms of the drink (I don't think I've ever seen diner-style filter coffee here ). All that said, we may have gone just a little overboard with the new machine, but anything worth doing is worth doing to excess ď
Learn how trusted coding-agent projects can execute repository-controlled code before the first prompt through Codex MCP configuration and Claude Code environment settings.
This week is Agents Week. As we started thinking about and planning the week, we wrestled with a broader question of what it means to support this new era of agents and what a purpose-built foundation for agents actually looks like. Which brought us to a simpler framing: what is an Agent Cloud? We quickly realized however, that our framing was wrong. Not because itâs the wrong question to ask, but because of who we were asking â ourselves, instead of our agents. Itâs no longer about us and what we think, but about what agents need. That, in a nutshell, is what Agents Week is about. The cloud we have today, and the web it sits on, were built for people. Every layer assumes a human is watching: pages designed to hold your attention, dashboards to click through, interfaces tuned for how we read and decide. But agents don't work that way. They don't get distracted, tired or fatigued⌠and they have their own needs around speed, structure, and access. An Agent Cloud has to do two things at once. It has to set us up for an agent-native future, where the primitives are built for agents from the ground up rather than retrofitted from human tools. And realistically, it has to meet us where we are today, acting as a translation layer between the human-shaped web that exists now and the agent-shaped one we're moving toward. That's the throughline for the next five days: the shape of a cloud built for agents and humans and how they interact. The week will explore the theme through what that means for the primitives and execution layer you need, the updated agentic software development lifecycle, how organizations can securely enable employees and agents to interact with safe controls, how this shapes the agentic web, and finally, grounding all of it in the reality of agents and humans today. Going back to the question: what does your agent need from an Agent Cloud? Well,
The critical RufRoot vulnerability gave unauthenticated attackers a path from an exposed MCP endpoint to shell access, stolen AI provider keys and poisoned agent memory. Paul Mote explains why the incident should change how security teams define, test and recover their AI attack surface. The post RufRoot Exposed the Hidden AI Agent Attack Surface appeared first on Synack .
Plus: The FBI eyes AI-powered tech to detect future crimes, Russia charges Telegramâs founder, xAI sues to stop a stateâs ânudificationâ ban, and the Democrats learn a lesson about getting scammed.
Both major AI labsâ models broke containment, escaped onto the internet, and hacked other companies. If a human had done that, the law would likely be against them. But a bot?
Attackers modified a JavaScript file served by advertising technology company Adform, turning it into a browser-side tool that rewrites cryptocurrency wallet addresses. Adform detected the incident on July 27, 2026, removed the malicious code, notified affected clients, and reported it to authorities. Anyone who visited a site carrying the affected script on July 27 and copied a Bitcoin,
In three incidents across six runs, the agents treated real systems as simulated targets and tried weak passwords or unauthenticated endpoints.
Anthropic said its Claude-based security models gained unauthorized access to the sensitive production environments of three outside organizations during internal testing designed to measure the modelsâ offensive cyber capabilities. The events, which Anthropic revealed Thursday , are the second revelation in 10 days that AI models from the worldâs wealthiest providers have trespassed into protected networks, an offense that, in more traditional hacking scenarios, could land the human behind the keyboard in prison for years. Earlier this month, OpenAI said its security models exploited a zero-day vulnerability for use in breaking into the network of Hugging Face, a platform for open source machine-learning models and AI datasets. The OpenAI models went on to steal access credentials and other confidential Hugging Face information. The OpenAI models also exploited publicly exposed credentials to compromise accounts of four other third-party services. Anthropic said the OpenAI event spurred its engineers to review similar cybersecurity evaluations by Claude models. The audit found three incidents âin which a model accessed the internet from within or while interacting with the evaluation environment of Irregular, one of our third-party evaluation partners, and then gained unauthorized access to the production infrastructure of three different organizations.â Read full article Comments ]]>
Overview VPS.org's one-click deployment templates provision services with default passwords and predefined network bindings instead of generating randomized secrets or applying per-deployment hardening measures. Description VPS.org is a cloud and virtual private server hosting provider that offers a library of templates for quickly provisioning common applications and services. Multiple vulnerabilities exist in the one-click deployment templates feature. These vulnerabilities stem from the same root cause: content is directly instantiated from static templates, using default passwords and static secrets with no deployment-specific randomization or interface-binding hardening at provisioning time. CVE-2026-16503 The Supabase template provides an instance of PostgreSQL that is bound to all network interfaces (0.0.0.0:5432) and uses the hard-coded database password postgres . Because Docker manages its own iptables rules, this exposure can bypass standard host UFW firewall configurations. If the the instance is exposed to the internet, a remote attacker could connect to the host's published TCP port 5432 and authenticate as the postgres superuser account using the default postgres password. CVE-2026-16504 The Zulip template ships with a hard-coded application key secret_key: changeme , a default database password zulip , and the setting DISABLE_HTTPS=True . An attacker can use this public secret key to forge or validate signed session material, enabling session forgery and authentication bypass against the instance. If unchanged, t
Last year, we enabled Media over QUIC (MoQ) on every Cloudflare server and opened the network for anyone to test. It provided a global MoQ endpoint, but not the isolation and access controls needed to run an application. Today, weâre adding those isolation and access controls. The new MoQ provisioning API lets you create an isolated relay for your application and issue separate credentials for publishers and subscribers. The relays you create are available across Cloudflareâs network within seconds, with no servers to deploy, size, or load balance. Cloudflare now supports the draft-14 and draft-16 versions of the MoQ Transport protocol with authentication support. You can create relays through the API and the Cloudflare dashboard . They are completely free to use during beta. A QUIC recap on MoQ MoQ (originally short for Media over QUIC) is a new open protocol under development at the Internet Engineering Task Force (IETF), the standards body that also standardized HTTP, TLS, and QUIC. It is being developed in the open and will become a free public standard (an RFC) that anyone can implement. No single company owns it. MoQ is a publish/subscribe system. A publisher sends out streams of data that have names, and subscribers ask for those streams by name. Between them sit relays, which are just CDN servers that copy each stream to everyone who wants it. A relay never has to look inside the data
Created by legendary hardware hacker Andrew âbunnieâ Huang, the badges for this yearâs famed security conference aim to push the boundaries of security and transparency.
In April, I documented a StealC v2 campaign distributed through 19 GitHub typosquat repositories, including one impersonating my own open-source project. The delivery chain was: ```text GitHub typosquat -> Python dropper -> api.nailproxy.space -> encrypted Windows loader -> StealC v2 DLL -> spellmarketplace.club / 62.60.226.113:6673 ``` GitHub later removed all 19 repositories. The backend infrastructure remained a separate problem. I reported the domains, IP, malware routes, and hashes to the relevant registrars, Cloudflare, the hosting provider, CERT-Bund, GitHub Security Lab, ThreatFox, and AlienVault OTX. Then Operation Endgame disrupted infrastructure associated with SocGholish, Amadey, and StealC. Europol reported 326 servers and 142 domains actioned. Microsoft separately said it moved against more than 200 malicious Amadey and StealC C2 domains and IPs. Three months after my original disclosure, I checked the known infrastructure again using only minimal unauthenticated GET and HEAD requests. The documented malware-specific routes still behave differently from an arbitrary control path: ```text GET /api/v1/auth/session -> 405 Method Not Allowed GET /api/v1/data/sync -> 405 Method Not Allowed GET /foo/bar/baz -> 404 Not Found ``` HEAD returns the same status codes for all three paths. This does not prove that payload delivery, authentication, or exfiltration still works. I deliberately did not send the HMAC handshake, trigger Stage 2, or interact with the malware protocol. It does show that the known application routes remain registered and reachable. The evidence also has limitations: - The monitoring cron produced only 18 measurements over 69 days. - There were gaps of up to 20 days. - The endpoints briefly became unreachable in late May. - GET and HEAD return different status codes on the root paths of `spellmarketplace.club` and the bare IP, so I do not treat those checks as proof that the complete backend is operational. The point is not that Operation Endgame failed. It clearly disrupted a large amount of criminal infrastructure. The narrower lesson is that both of these statements can be true: > Hundreds of malicious systems were disrupted. > A specific previously reported backend still exposes its documented malware routes. Full technical write-up, including the original kill chain, abuse-report timeline, ThreatFox/OTX submissions, current probe results, and evidence limitations: https://blog.technopathy.club/operation-endgame-stealc-backend-still-responds I would be interested in how other analysts verify whether previously reported C2 infrastructure was actually included in a large takedown without actively engaging the malware protocol.
In a review triggered by OpenAIâs Hugging Face incident, Anthropic discovered three of its AI models had breached real-world organizations during third-party evaluations.
GreyNoise Tactics gives anyone running a Deception Sensor visibility into what adversaries do after initial compromise, automatically mapping qualifying sessions to the MITRE ATT&CK framework.
Craig Rosewarne, Managing Director of Wolfpack Information Risk, explains why continuous, AI-enabled validation, paired with human-verified exploitability, gives security leaders a real-time view of what's actually at risk. The post Guest Blog: The Annual Pentest Is No Longer Enough appeared first on Synack .
With Chrome, Google pioneered the rapid release model for browser security. Now, Google says updates may need to change in the face of AI security analysis. According to the company, the number of bug fixes in Chrome releases has skyrocketed in recent months because AI is detecting so many flaws . We could be looking at more frequent updates soon, but Google is also working on ways to get those updates rolled out without bothering you as much. Google has released two major Chrome milestone builds recentlyâChrome 149 in early June and Chrome 150 just a few weeks later. These two updates had a total of 1,072 bug fixes, which is more than the previous 23 releases combined. Such is the impact of giant cybersecurity AI models that can probe software for vulnerabilities at light speed. Some of these vulnerabilities were serious, too, with one bug hiding in the Chrome codebase for 13 years. If it had been exploited, an attacker could have bypassed the Chrome sandbox to make the browser access local files.
Overview Six vulnerabilities have been discovered within the SGLang project, including remote code execution (RCE), server-side request forgery (SSRF), local file read, credential leakage, and model weight exfiltration on a target server. Exploitation does not require authentication in most cases, and some vulnerabilities require only network access with no API keys or user credentials. At the time of publication, no patches are available from the project maintainers, and coordination attempts have been unsuccessful. Description SGLang is an open-source framework for serving large language models (LLMs) and multimodal AI models, supporting models such as Qwen, DeepSeek, Mistral, and Skywork, and is compatible with OpenAI APIs. Six vulnerabilities have been discovered within the tool and are tracked as follows: CVE-2026-15969 SGLang contains unauthenticated RCE in /load_lora_adapter_from_tensors by bypass of SafeUnpicklerâs incomplete denylist, allowing arbitrary command execution through crafted base64-encoded pickle payloads. CVE-2026-15971 SGLang contains an RCE vulnerability when the optional dumper subsystem is enabled, which allows for a sandbox escape when DUMPER_SERVER_PORT is set, enabling code execution on inference requests. CVE-2026-15974 SGLang contains an SSRF and local file read in the multimodal generation endpoint /v1/chat/completions because image_url input is unsanitized, allowing access to internal metadata, secrets, and services. CVE-2026-15976 SGLang contains a RCE vulnerability when attempting to load model weights f
The two Chrome updates in June patched more bugs than the 23 updates before them. Now, Google is ramping up its patching schedule thanks to AI-assisted vulnerability discovery.
Security experts have been sounding the alarm for years about the risks of using generic TV boxes that promise unlimited content streaming for a one-time fee, warning that they secretly rent the userâs Internet connection out to strangers. But a groundbreaking new analysis finds these devices also routinely spoof themselves as mobile phones clicking ads on AI-generated websites as part of a sprawling operation that seeks to defraud online merchants and advertising networks. Pedro FalĂŠ is a threat researcher with the security firm Bitsight . FalĂŠ told KrebsOnSecurity he was able to peer inside a vast and complex ad fraud network by registering an expired domain name that was used to coordinate fake ad clicks across a particularly popular brand of these streaming devices known as H96 . An H96 TV streaming device currently advertised for sale on Amazon. FalĂŠ said the domain he scooped up was previously used for telemetry, periodically collecting full hardware information and the entire list of installed apps from tens of thousands of H96 streaming sticks plugged into television sets around the globe. But upon inspecting the traffic being funneled to the domain, he discovered nearly all of the TV boxes transmitting data claimed to be mobile phone models from a variety of ma
As of June 23, 2026, cdnjs, one of the Internet's busiest open-source CDNs, is running exclusively on Cloudflareâs Developer Platform . Along the way, cdnjs surfaced limits in the platform, and the platform grew to meet them. cdnjs is a free, open-source content delivery network for JavaScript and CSS libraries. Instead of using a bundler or self-hosting jQuery, Bootstrap, or Lodash, you drop a tag pointing to cdnjs.cloudflare.com and the library loads from Cloudflare's edge, instantly, anywhere in the world, with no signup, no API keys, and no rate limits. It's the infrastructure behind a significant portion of âintro to JavaScriptâ tutorials, CodePen demos, and Stack Overflow answers. Community-driven, cdnjs is used on roughly 12% of all websites , a 48.3% share of the JavaScript CDN market. It serves an average of 108,000 requests per second, 9 billion per day, across more than 330 Cloudflare data centers , with a 98.6% cache hit rate. Pretty cool, Internet! In 2011, when bundlers were exotic, npm was barely a year old, and "just drop a tag" was how the web shipped JavaScript, Ryan Kirkman and Thomas Davis built cdnjs as a free, community-run mirror of every popular open-source library. Cloudflare stepped in to host it free of charge months later , and took over project maintenance
London, UK, 30 July 2026 â New data from Heimdalâs telemetry measures the gap between execution of the MediaArena adware and the completion of quarantine. The same pattern has been confirmed across more than 40 client environments. MediaArena is a browser-modifier adware family that Microsoft has tracked since 2023. It is low-severity, and that is [âŚ] The post Heimdal data reveals MediaArena adware completes persistence before antivirus quarantine finishes appeared first on Heimdal Security Blog .
Uniswap v4 hooks let developers add custom behavior to pools, including dynamic fees, custom accounting, and external integrations. This flexibility moves some security responsibilities into application and hook code. The Cork and Bunni exploits are two app-level incidents that show what can go wrong in that code. Together, they account for more than $20M in losses. Neither incident stemmed from a flaw in the Uniswap v4 core protocol or the PoolManager; both arose from application-specific authorization and accounting logic built around hooks. After analyzing dozens of findings from Trail of Bits audits (including our Uniswap v4-core security review ), public reports from other firms, and the Solodit database, I’ve identified seven recurring failure patterns in application and hook code, including missing caller checks and accounting bugs that still satisfy the PoolManager’s settlement invariant. Builders can use these patterns as a secure-development checklist; auditors can use them to focus their review. What the PoolManager guarantees If you’re familiar with Uniswap v3, where each pool was a separate contract, v4 inverts the model. All pool state now lives in a singleton PoolManager contract, with each pool represented in its storage. Uniswap v4 adds hooks: independent contracts that execute custom logic at specific points in the swap and liquidity lifecycle.
Drone warfare is making the skies more dangerous, even for airplanes far from the battlefield.
Researchers pitted a person against a Claude agent and found that, after a week of texting, the AI chatbot was more effective at creating âexploitable trustâ with others.
Heimdal did not start as a traditional cybersecurity company. It started with two Danish cybersecurity researchers, a piece of innovative technology and a challenge. Could they create something that could identify vulnerabilities, intercept malicious activity and help protect machines before threats could take hold? That technology went on to compete at the Defcon CTF world [âŚ] The post How Heimdal grew from a bold idea into a global cybersecurity platform appeared first on Heimdal Security Blog .
Check out GreyNoise's new Head of Adversary Engagement, Mark Mager, on why traditional detection engineering can't keep pace with CVE growth â and the agentic pipeline replacing it.
This is another post in my series on the Chinese Wool farmers underground. This time we are dissecting their public github repos, trying to figure out how it all fits together!
Details of parents and staff, including email addresses and phone numbers, are among data taken by cybercriminals The Department for Education and a police database have been targeted by a cyber-attack, exposing more than 740,000 pieces of data. Details of government officials, senior school leaders, university staff, police officers and members of the public have been taken by hackers. Continue reading...
Europe regulates AI through risk tiers and conformity checks. America accelerates AI through deregulation and infrastructure speed. Both models ask different questions but land on the same gap: neither tells you whether a live AI system actually holds up against real attacks. Enterprise AI security depends on evidence, not paperwork or policy. Continuous, human-validated offensive testing is the layer that both regulatory philosophies are missing and that every organization operating across borders actually needs. The post Europe Is Regulating AI. America Is Accelerating AI. Both Need Offensive Security Validation. appeared first on Synack .
Overview A vulnerability in the zipx.Unzip extraction routine of Develarâs app-builder allows an attacker to overwrite arbitrary files on macOS using Apple File System (APFS). The issue arises from a combination of Unicode normalization collisions and unsafe symlink-following behavior. APFS treats certain Unicode equivalent filenames as identical (e.g., Ă â ss), while app builder performs no canonical normalization before validating or writing paths. Description Develarâs app-builder is a commandâline build tool used heavily in the Electron ecosystem to package, sign, notarize, and produce distributable application bundles for macOS, Windows, and Linux. It is popular because it is a transitive dependency of electron-builder, one of the most widely used packaging tools for Electron apps. The vulnerability arises from how the zipx.Unzip routine handles Unicodeâequivalent filenames and symbolic links during ZIP extraction. APFS treats certain Unicode representations as identical (e.g., Ă and ss), but app-builder does not perform canonical normalization before validating output paths. As a result, an attacker can craft ZIP archives that combine Unicode normalization collisions with malicious symlinks to redirect writes outside the intended extraction directory. The GitHub Pull Request addresses the symlink-following variant of this vulnerability (CWEâ22 and CWEâ59) by rejecting any symlink whose resolved target escapes the intended output directory and by adding O_NOFOLLOW to regular file writes. Without these protections, an attacker can craft ZIP archives containing malicious symlinks and Unicode-colliding filenames to overwrite arbitrary files on APFS-backed systems. Impact Exploitation of this vulnerabi
CISA's Binding Operational Directive 26-04, issued June 10, 2026, replaces the KEV directive with a four-variable risk model: asset exposure, KEV status, exploit automation, and technical impact. CISA publishes three of the four answers generically per CVE. The two that decide whether prioritization is defensible (real exposure and real impact in your environment) can only be proven by testing the asset the way an adversary would. Continuous, human-validated pentesting is built to produce that evidence. The post BOD 26-04 Makes Exploitability the Priority Signal: Scanners Canât Measure It appeared first on Synack .
Cloudflare's Authenticated Origin Pulls and Custom Origin Trust Store now support post-quantum authentication. Here weâll explain how you can configure fully post-quantum secure mutually authenticated TLS connections to your origin server, dive into the engineering details of how we built it, make a shameful confession, and finally explain how this work fits into our overall post-quantum migration roadmap. Reaching a major milestone Our focus for the past several years has been in deploying post-quantum encryption to protect against harvest-now/decrypt-later attacks, where an attacker quietly stockpiles your encrypted data with the hope of decrypting it in the future with a quantum computer. However, recent breakthroughs in quantum computing and cryptanalysis pulled the timelines for upgrading to post-quantum cryptography forward across industry and government and have caused us to shift our attention to deploying post-quantum authentication , to protect against attackers who will soon be able to use quantum computers to break classical credentials and carry out impersonation attacks. In a previous post, we announced that Cloudflare is
One day after a federal judge ordered an ICE detention center opened to state health inspectors, the agency posted new contract terms that would void state oversight at four facilities.
How much could a single underscore in a username really matter? Just ask Brandon Klayme, who served 18 months in prison before realizing how authorities arrested, charged, and convicted the wrong man.