FrameworkGuidesModulesRelease NotesAbout

On Your Mark, Get Set, Go — May V-Day

With the May V-Day release approaching, this post covers what the update includes, how to prepare your testing environment, and what defensive teams should plan for when the updated framework becomes available.

What to Expect

The May V-Day update brings several changes to the framework's payload generation capabilities. Updated templates, improved encoding options, and bug fixes accumulated over the preceding months are bundled into a single release for thorough testing before deployment.

Each V-Day follows the same pattern: the development team freezes new features several weeks before the release date, focusing the final stretch on testing, documentation, and regression verification. By the time the release ships, every change has been validated against the supported target environments.

Preparing Your Lab

Before applying any framework update, your lab environment should be ready:

For Offensive Teams

  • Snapshot your current testing environment before upgrading
  • Document your current payload configurations so you can regenerate them with the updated version
  • Clear the framework's cache and temporary directories
  • Verify your Python environment matches the updated requirements

For Defensive Teams

  • Update your detection test suite to include current baseline results
  • Prepare your monitoring stack to capture events from updated payload types
  • Schedule time to re-run detection tests after the update is applied
  • Review the release notes for any changes that might affect existing detection rules

The V-Day Cadence

The scheduled release model gives both offensive and defensive teams time to prepare. Unlike rolling updates that can catch people off guard, V-Day releases are predictable. This predictability is a feature — it allows for structured, thorough evaluation rather than reactive scrambling.

Post-Release Verification

After applying the update:

  1. Generate a set of test payloads across all supported languages
  2. Deploy each to your monitored lab targets
  3. Verify detection coverage against your existing rules
  4. Document any changes in detection results
  5. Update detection rules as needed

Related