Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

We released a new public tool, 3LayersPersistence, that demonstrates 3 different persistence layers implemented in one executable. The implementation uses WMI event subscriptions, DLL sideloading, and COM hijacking in a single workflow, with the executable patching itself into proxy DLLs at runtime, allowing execution through multiple persistence paths.

12,054 Aufrufe • vor 3 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

So, let me get this straight SpaceWeatherNews . Earth’s magnetic field is weakening right now, and it’s happening faster than expected. When you look back, the record shows the field didn’t always drift slowly either, sometimes it collapsed and re organized and things got beyond chaotic. The Sun isn’t a campfire in the sky like we were taught, it behaves in cycles and it can get violent in ways we’re only starting to understand. Earth reacts electrically and magnetically, like a living system kinda like bieng plugged into the Sun. Ice cores, tree rings, and archaeological layers all show resets happening at the same times around the world. Not once, but repeatedly. It's a clear pattern. We have direct measurements showing Earth’s magnetic field has weakened significantly in just a couple of centuries, with anomalies growing and the poles accelerating in ways that match pre excursion behavior seen in the geological record. We have lava flows that lock in multiple magnetic directions in a single cooling event, proving the field can shift rapidly, not over slow timelines. We have ice cores and tree rings showing abrupt spikes in cosmic radiation markers like carbon 14 and beryllium 10 that appear globally and simultaneously, which only happens when shielding fails or solar input surges. We have sudden climate reversals, where temperatures jump or crash in decades. Something standard models still have a hard time to explain. And we have synchronized layers of environmental fails in human history. We have abandoned settlements, cultural collapses, and reset layers that line up with those same physical events. None of this is speculative on its own. This is not speculation or fake, these are connected, because we have the individual datasets, they have been peer reviewed, and is sitting in plain sight. Forget the aliens for a second because we have some preparing to do.

Jason Wilde

46,819 Aufrufe • vor 4 Monaten

Beauty ads just changed forever. Free Claude Opus 4.8 + GPT Image 2 + Seedance 2.0 workflow to spin up 100s of video ads. No studio, no model, no macro lens, no shoot day. Here's what nobody in beauty marketing wants to say out loud. That glossy lip shot. The droplet hitting the surface in slow motion. The whip-pan into the next scene. The crystalline product splash. All the stuff that used to need a real set, a real camera op, and a full shoot day. You can generate every frame of it from a text prompt now, and stitch it into a finished ad before your coffee goes cold. The workflow is almost stupidly simple: → Tell Claude Opus 4.8 the beauty shot you want (dewy skin macro, gloss-on-lips contact, ripple transition, the works) → Claude turns it into a shot-by-shot storyboard plus a prompt for every frame → GPT Image 2 generates the photoreal stills, frame by frame → Seedance 2.0 animates each one into a clip with that buttery slow-mo glide → You drop the clips into HeyOz and assemble the full ad in one place The real unlock is volume. This isn't one hero video. Once the workflow is dialed, you spin up hundreds of variations. Different shades, different models, different hooks, different transitions. The exact creative volume Meta rewards, minus the production cost that used to make it impossible. Old way: one shoot, one look, $10k+, weeks of waiting. New way: a hundred angles, any look, a few dollars each, same afternoon. I wrote up the entire workflow. The Claude storyboard prompt, the GPT Image 2 frame prompts, the Seedance motion settings, the full assembly flow. Completely free, no email gate. Want it? Comment "GLOSS" and I'll send it straight over. (make sure you're following so it can actually reach you)

Ahad Shams

10,957 Aufrufe • vor 1 Monat

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 Aufrufe • vor 4 Monaten