Minor Release 7.1, 7.2
Deployed: 14 May 2026 AEST
Fixes
- Profiling & detection: Backfilled journey start timestamps on older records that had been written in milliseconds instead of microseconds
- Portal: Resolved JWT refresh token failures that were logging users out mid-session
Minor Release 6
Deployed: 6 May 2026 AEST
What's new
- Portal:
- Added context searching to Labels View
- Added scope radio buttons to the CheckLabel helper inside the Rules Editor
- Features Editor now includes inline validation
- Export to .csv from Investigations view is now supported on Darwinium hosted buckets.
- Customer hosted buckets to follow, including performance improvements on exports exceeding 100k rows.
- Edge & deployments:
- Cluster upgrade buttons now highlight orange when a Kubernetes upgrade is pending
- Added Encrypted Cookie support for stronger session integrity at the edge
- Added Node.js 24 runtime support on CloudFront
- Cloudflare and CloudFront edges now use a unified secret management flow, with secret refresh on the CloudFront Lambda worker
- Added a healthcheck endpoint and
g6-dedicated2node type support for Linode, alongside resource tuning - Improved Akamai build logging verbosity
- Privacy (SPII / IBD):
- Sensitive PII (SPII) is now supported end-to-end across collection, storage, and decryption, with a dedicated encryption key and permissions flag
- Those attributes labelled SPII will be hashed for all users without the SPII permission
- Profiling & detection:
- VPN profiling model detection now incorporates Android SDK network transport type
- JS profiling detects Chrome developer tools being opened
profiling.javascript.developer_mode - Network filter now captures TCP segment lengths
- Rules & configuration:
- Enum attributes, those with fixed list of expected values, now are validated.
Enum validationIf provided a value not in expected list, event will still execute and return response, but will have response code 422 and invalid value reported in
invalid_input_attributesand Portal event sidebar- national_id type/geo combinations are validated (e.g. a Thai ID with a US geo now correctly raises an error)
- Email sub-attributes auto-populate from the parent email field
- Phone dial code and geo can now be labelled.
- New identifier attribute:
identity[*].crypto_wallet.address - Added
bank_codeas a recognised standard forbank_account.standard national_id.expiry_datecan now be queried directly- passport now resolves a
national_id.identifier. The type, national_id and geo attributes are mandatory to resolve. ISO3 can be used as input geo, will be converted to ISO2.
Example:
{
"identity": {
"ACCOUNT": {
"national_id": {
"type": "passport",
"national_id": "123456789",
"geo": "GB",
"expiry_date": "2030-12-31"
}
}
}
}
Fixes
- Portal:
- Fixed dragging existing rules into an empty group in Rules Editor V2
- Fixed
is_system_user: falserendering as null in Investigations events grid - Corrected
device.identifiermixing up when comparing two events zip_post_codenow displays in events- Improved stability of token refresh and session timeouts when multiple tabs are open
- Resolved GraphQL errors on the Labels page
- Edge & deployments:
- CloudFront preflight (OPTIONS) handling and a content-length-zero issue on responses
- Page injection in
edgeworker_fullmode
- Rules & configuration:
- Journey checker error messages when the rules file cannot be located
- Jinja template support for hyphenated step names, including a fix for Speedbump profiling
national_id.geono longer defaults to a US location for invalid input
- Profiling:
- Missing attributes when
cacheable_javascriptis enabled and the network is blocked
- Missing attributes when
Minor Release 5.5
Deployed: 16 April 2026 AEST
What's new
- Edge & deployments:
- Edge nodes can now route different paths to different upstream origins, with the Host header rewritten correctly for each
- Added
edge_connection.response.durationas an attribute available to rules and queries - Increased response header buffer and removed the cap on client body size for edge requests
- Fixed CloudFront deployment failures triggered by a tightened length limit on the AWS Comment field for new functions
Minor Release 5
Deployed: 24 March 2026 AEST
Fixes
- Portal: Reclassified Scam categories from Neutral to Negative context to reflect their actual risk weighting
- Edge & deployments:
- SNI configuration values now stay cleared after saving
- Fixed an Akamai redeploy error caused by a missing deployment record
Minor Release 4
Deployed: 19 March 2026 AEST
Fixes
- Edge & deployments: Worked around an upstream provider issue causing intermittent 500 responses when fetching firewalls, by switching to label-based filtering
Minor Release 3
Deployed: 17 March 2026 AEST
What's new
- Portal: Rules Editor V2 now shows dependency warnings, flagging references that would break at build time
- Edge & deployments:
- Added full deployment mode for Akamai edge workers
- Upgraded Linode Kubernetes for security and stability
- Profiling & detection:
- Chrome developer tools usage is now reported through to the API server as a profiling signal
- Rules & configuration:
- Feature Editor event types are now sourced from our central configuration so they stay consistent platform-wide
- Added handling for the new bot event type in the engine's bot check logic
Fixes
- Portal:
- Rules Editor save race condition
- Events grid pagination on large result sets
- Investigations date widget changing the selected range
- Timestamp edits being applied without confirmation
- Labels view filter widget on composite identifiers
- Quantile value rounding mismatch
- Deployment status stuck on "deploying" after build completion
- Custom Features now appear in the sidebar after an Update Event API call without a full reload
- Profiling:
- Removed an over-matching condition that merged distinct device IDs
- Android display status now reports
STATE_ONcorrectly
- Rules:
- Journey language service now flags invalid
event_typevalues - Journey transitions now run for newly added steps
- Journey info restored on identifier records
- Journey language service now flags invalid
- Plus backend stability work covering API request handling, cross-node auto-refresh, database query errors, and a Speedbump regression
Minor Release 2
Deployed: 25 February 2026 AEST
What's new
- Profiling: Updated the Darwinium profiling snippet to detect when a browser opens developer tools
Fixes
- Rules:
- TypeScript export no longer throws when rules contain type mismatches or duplicate feature names
- Named signals preceded by a leading exclamation mark are now correctly flagged
Minor Release 1
Deployed: 24 February 2026 AEST
Fixes
- Portal: Notes attached to labels now display correctly in the Label view
- Rules: Named conditions no longer raise spurious errors
- Performance improvements to journey ID identifier writes