AuditTeam/OpsAgent: driver and backup risks in new research
A technical brief on Kaspersky's November 18 research, separating vendor observations from defensive assessment.
Updated: · Vietnam time (UTC+7)

Research checked; samples not reanalyzed. Attribution is the vendor's assessment; leak-site claims remain independently unverified.
Research published November 18, 2026 about an earlier campaign, not a new Vietnam incident notice.
Vendor-reported evidence
Kaspersky describes OpsAgent, a signed-driver process-killing module and an encryptor affecting databases and backups. [S1]
The GitHub repository was removed in November, but newer Rust implants can disable that mechanism. Removal does not establish the campaign's end. AI involvement remains an assessment. [S1]
Editorial assessment: detection and recoverability first
Ransomware.VN suggests correlating protection and backup service changes across multiple artifacts rather than relying on a filename or a signed driver alone.
- Compare driver installation, parent/child processes and service stops with approved changes.
- Keep recoverable copies under separate administrative authority and test restoration in isolation.
- Do not identify a family from a lone ransom note or treat an extortionist's deletion promise as proof of deletion.
- This brief issues no new IOC; SOC teams should review the original research and validate scope before blocking.
Sources
Each source's scope and date are recorded separately when available. A citation does not independently verify every assessment.
Update history
· Initial VI/EN publication; stated attribution, claim and AI-assessment limits.
Corrections policy