securitylab_nJuly 12, 2026🇷🇺Translated from Russian

Bacteria Convert Toxic Dissolved Uranium into Rare Stable Compound FeU(V)O₄, Paving Way for Microbial Nuclear Waste Remediation

Researchers studying microorganisms naturally living in a flooded uranium mine in the Ore Mountains have uncovered an unexpected biological mechanism that could help address one of the most persistent challenges in nuclear waste management. The bacteria do not merely absorb dissolved uranium from water; they actively convert it into a rare and chemically stable compound previously thought to form only under very specific geological conditions.

The experiments were conducted using real mine water containing dissolved uranium under strictly anaerobic conditions that replicate the oxygen-free environment found at depths of approximately 2 km. When the scientists added glycerol — a widely available compound found in plant and animal fats and produced during fungal decomposition of wood — as the sole additional carbon and energy source, the bacterial community began to thrive rapidly.

After 130 days, only about 5% of the original dissolved uranium remained in the water. Initial assumptions that the metal was simply accumulating on bacterial cell surfaces were quickly disproven by detailed microscopic and spectroscopic analyses performed at the European Synchrotron Radiation Facility (ESRF) in France, which allows atomic-level examination of materials.

The results showed that a significant portion of the uranium had been reduced to the uncommon pentavalent state (oxidation state +5). This form is normally unstable and quickly converts to more common +4 or +6 states. In this case, however, the pentavalent uranium reacted with iron and oxygen to form the mineral FeU(V)O₄, a compound first discovered only in 2020 in uranium-contaminated soil in Croatia that had remained stable for over 25 years despite exposure to atmospheric oxygen.

Further tests revealed an even more surprising property: when the bacterial biomass was dried and subsequently exposed to oxygen, the amount of FeU(V)O₄ continued to increase rather than degrade. This indicates that oxygen can, under certain conditions, actually promote the formation and persistence of the stable uranium compound.

The findings open new possibilities for bioremediation — the use of living organisms to clean contaminated environments. Current methods for removing uranium from water and soil are expensive and technically complex. If the microbial process can be harnessed effectively, it may provide a sustainable, low-cost alternative for treating former uranium mining sites and other contaminated areas.

Nevertheless, the researchers emphasize that the work remains at the laboratory stage. Future studies will focus on identifying the specific bacterial species responsible, understanding the underlying biochemical pathways, and testing whether the same transformation can be reliably achieved and controlled under real-world environmental conditions.

Related articles

HabrOther

OAuth Authorization Server Built Without Storing User Profiles

The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.

HabrOther

Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA

A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.

HabrOther

Pilcrow Publishes Free Comprehensive Guide on Web Authentication

Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.

HabrOther

redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem

redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.