Kategorie
Security, security, security: What a week of outages means to IT (and you)
The last week of major security and resilience problems is proof that business and consumer users must think just as deeply about tech resilience as any big enterprise.
The pace at which major outages have impacted major entities in the last few days will already have had an impact on business, imposing real consequences.
A week IT leaders can’t ignoreThe incidents are very hard to ignore. Microsoft’s major outage November 12-13 took out Microsoft 365 services for an unacceptable 24 hours, and the FAA grounded US flights for more than four hours on Nov. 13 because of network equipment outages. This week, a JPMorgan Chase outage rippled throughout the financial system, United Airlines experienced a widespread system outage, the US National Security Agency’s classified internal network went down, and then many of Apple’s own systems also hit problems. (Officials do say all these incidents were not connected other than by temporal proximity.)
Apple’s big outage saw several of its enterprise and consumer services fail. These included iCloud sign-in and backups, Apple Pay, the App Store, and Apple Support. It also extended to developer services such as App Store Connect and Xcode Cloud and the company’s own internal corporate tools, including AppleWeb. Internal system failures meant physical Apple Store retail operations were also hobbled, disrupting sales, customer pickups, and device repairs.
There were reports that device management onboarding was briefly out of action, while others reported errors setting up new iPhones. Apple moved quite swiftly to resolve the problems inside working hours, from when they were first reported at around 11:45 a.m. ET to full restoration at around 6 p.m. ET.
So, was it a hack?Apple said it was not caused by a cyberattack and has given no indication that personal data was put at risk. The company told NBC News that the disruption was caused by an internal update but didn’t say anything at all beyond that.
“Many of our systems are back up and running after an internal update caused some outages this morning,” Apple said. “We’re working to get the remaining systems online as soon as possible.”
Whatever Apple did seems to have worked. As of this morning, DownDetector shows Apple’s services working normally even though Apple’s developer services page shows an outage with App Store Connect.
We don’t know what failed or why the update generated what could be multiple failures across Apple’s systems, each of which rely on their own infrastructure. We don’t know why the problem wasn’t caught in staging or contained within a staged rollout. Nor do we know if the failure took place at a shared layer, such as identity or authorization, and we aren’t likely to know unless Apple publishes a post-incident report.
Shared layers, multiple dependenciesThat leaves us with conjecture. One possibility: the manner in which the failure manifested itself points to a shared dependency. Sign-in, payments, developer authentication, and internal staff tools all depend on authorization, so a problem there may have taken down services with otherwise unrelated back ends. A fix applied to a shared layer would fit a recovery by close of business, but so would a rollback of whatever update Apple applied.
At the same time, the cascading nature of the problem shows just how much we all rely on digital infrastructure and the extent to which any failure in those systems threatens businesses and end users. The timing of these incidents couldn’t be worse as global governments continue to tell citizens to prepare bug out bags for use in emergencies, raising the general sense of fear and uncertainty.
Resilience isn’t glamorousApple hasn’t said whether it will publish a post-incident report, so unless it does, the safe conclusion is that an internal change broke something shared, that personal data appears unaffected, and that the rest is unknown. But what isn’t resolved is how consumer and business users are meant to protect themselves and their own business continuity when two of the world’s leading computing platform providers hit serious outages within a week.
We must get better prepared for such challenges. The practical response is to identify which critical processes depend on a single provider, maintain a recovery path that doesn’t run through that provider, and be ready to distrust unexpected “fix it” messages. Staff locked out of sign-in or any other service should be encouraged not to use unsanctioned tools or share credentials but to wait for the situation to be resolved or use a sanctioned fallback if one has been specified.
Now please subscribe to my daily, human-curated Apple-related news headline feed at The Core, or follow me on BlueSky, LinkedIn, or Mastodon.
Microsoft’s Agent Framework PyPI package compromised to steal credentials
From Deepfakes to Helpdesk Impersonation: Why Stronger Verification Matters
New EggStreme Malware Variant Goes Silent to Evade Security Tools in Government Attacks
New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years
AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor
Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More
Dizigom illegal streaming service with 21M monthly visits shuts down
Tohle je 20 nejpoužívanějších hesel v Česku. První není „heslo“ ani „123456“
Quality Isn’t The Main Worry About AI Pentesting — Data Privacy and Production Safety Are
A refreshingly practical hidden Gemini treasure
A fascinating contrast is shaping up around us here in the land o’ Googley matters, seemingly more with every passing month.
On the one side, you’ve got Google, who’s dead-set on pushing Gemini into every place possible and doing everything in its power to convince us to use it — in spite of its alarming little habit of, y’know, getting stuff wrong. More often than not, the company (like most tech players these days) is also focused on impractical processes and overly complex use cases that few actual humans have any interest in embracing.
On the other side sits us — the (allegedly) human mammal-people who are toting around all this technology, often begrudgingly, and mostly just looking for simple ways to make it more useful and simultaneously less intrusive in our lives. With exceedingly rare exception, nearly everyone I’ve chatted with in 2026 shares the same basic sentiment — that AI feels invasive and annoying, that most of what it’s offering has nothing to do with our current wants and needs, and that the type of tech we actually want somehow keeps getting worse as a result of its intrusion.
We need look no further than the Google Assistant-Gemini contrast on Android or the frustrating devolution of so-called smart speakers and screens for some all-too-relatable examples.
That’s why I, like so many of you, mostly roll my eyes at every new AI announcement and its lack of any real impact on my day-to-day life. And that’s also why I’m constantly on the prowl for ways Gemini can actually be useful when it comes to real-world productivity.
Perhaps not surprisingly, the discoveries that resonate the most tend to be the simplest, least flashy features imaginable — and that’s absolutely the case with the genuinely useful Gemini gem I want to share with you today.
[Get fresh tips in your inbox with my free Android Intelligence newsletter — something new and useful from me to ye every single Friday!]
Gemini’s quiet contact creating capabilitySeriously — this is so simple, it’s almost silly. It isn’t an effective illustration of the sheer processing power of the latest Gemini 7.23b Bouillabaisse model (which I’m fairly certain was the subject of a recent announcement somewhere).
But, unlike most of that malarkey, it’s actually something you’ll use and that’ll make your life easier. (Imagine that!)
It’s a quick ‘n’ easy way to import anyone’s information into a properly formatted, ready-to-roll contact on your phone with approximately seven seconds of active effort. And it works in two equally useful ways:
First, the next time you encounter an actual printed business card out and about on your adventures, fire up Gemini, tap the plus icon within its prompt box and select “Camera,” and snap a fast photo of the card — then just tell Gemini to save that as a new contact.
The very first time you do it, you’ll have to grant Gemini access to your contacts and all of that. But once that’s out of the way, the system will simply scan the info, put all the details into all the right places, and confirm that you want to save it.
A fast photo and confirmation, and our complete new contact is created.JR Raphael, Foundry
A quick confirmation later, and boom: That person is officially in your contacts, without the need for any third-party importing apps or time-wasting manual entry.
Every last detail visible on the card is present in the right place in the Contacts app.JR Raphael, Foundry
Second, this same feat will work with any virtual contact info you encounter anywhere on your device — in an email, on a website, you name it. Whenever you’re looking at someone’s info on your screen, just fire up Gemini and ask it to save the info you’re seeing as a contact. It’ll handle it in the exact same way.
Whether the info is on a physical card or on your screen somewhere, the contact-creating process is essentially the same.JR Raphael, Foundry
It may not be the kind of thing that’ll make it into the next big Google keynote or Gemini announcement, but it is the kind of thing you’re actually likely to use and appreciate in your day-to-day doings. It’ll make your life easier in a small but significant way — which, in my book, makes it exactly the flavor of feature that’s well worth remembering to embrace.
Keep the practical knowledge flowing with my free Android Intelligence newsletter — a single new and useful tip in your inbox every Friday.
Apache warns of Roller RCE vulnerability exploited in attacks
Navštívili jste v poslední době tyto weby? Vaše údaje už možná mají hackeři
Microsoft announces Windows Server 2028 with hardened security
Hackers Exploiting Critical Puppet RCE Flaw Affecting Enterprise Management Servers
CISA Urges Immediate Patching of Java4Shell Flaw That Could Allow Remote Code Execution
British Scattered Spider hacker sentenced to 6 years in prison
The forced audit: how AuditTeam’s OpsAgent framework masks ransomware as consulting
AuditTeam is an active threat group that uses the OpsAgent framework to compromise organizations across at least seven countries and territories. The campaign began in January 2026 and remained active through October 2026, at a minimum. In its ransom note, AuditTeam demands an “Audit & Consulting fee” in exchange for vulnerability reports. During this period, the group has infected dozens of organizations in Russia, Italy, the Philippines, Hong Kong, Senegal, Finland and China. The group’s leak site also claims victims in seven additional countries.
OpsAgent provides file system management, process injection, privilege escalation, keylogging, screenshot capture, and network pivoting. During the campaign OpsAgent was transitioned from C++ to Rust while adding new capabilities including interactive shells and WebSocket upgrades. Its command-and-control domains use Amazon CloudFront subdomains, which OpsAgent discovers via a public GitHub repository. Two specialized modules extend its functionality. An antivirus/endpoint detection and response (AV/EDR) killer module installs a digitally signed Beijing Jiangmin Antivirus driver to terminate security products. A cryptor module encrypts files using AES-CBC or ChaCha20 with X25519 key exchange and targets database processes for termination prior to doing so.
BackgroundOn March 10, 2026, we discovered suspicious activity targeting an organization in Hong Kong. The tool used was OpsAgent, a framework designed to resemble a penetration testing utility. Further investigation revealed attacks in additional countries, prompting an active research phase. This implant offers extensive operator capabilities, including host reconnaissance, shellcode injection via named pipes, and lateral movement through agent networks based on compromised hosts.
Analysis indicates OpsAgent was used by AuditTeam. The group was first mentioned publicly by dbdigest.com in March 2026. On June 25, 2026, DeXpose reported that AuditTeam had claimed responsibility for an attack on a Russian organization and listed it on its leak site. AuditTeam leaves a ransom note threatening to release stolen data unless a fee is paid. They call this fee the “Audit & Consulting fee.” According to the note, payment results in a vulnerability report being delivered to the victim instead of leaking the stolen data archive to the public internet. While the note does not mention file encryption, it is left by the cryptor module. Therefore, if a victim sees the note, their files are already encrypted.
The ransom note
GitHub commit history shows the campaign started on January 5, 2026. The leak site lists its first victim on February 21, 2026. Dozens of machines across at least seven countries were infected. On August 19, 2026, a C2 domain for the new OpsAgent version was added to the public repository and subsequently used in attacks.
AuditTeam activity timeline
Technical details LoadersOpsAgent uses multiple loader variants during its campaign. All discovered loaders unpack OpsAgent by parsing the MZ header and transferring execution to the entry point of the unpacked payload.
The C loader was discovered in April 2026. It injects shellcode into msiexec.exe using standard API calls: CreateProcessA, VirtualAllocEx, WriteProcessMemory, and CreateRemoteThread.
The .NET loader was found in June 2026. It uses NtQueueApcThread instead of direct process creation for injection. It contains strings such as DApc, DProtect, DResume, and msiexec.exe. Both the C and .NET loaders inject shellcode into a separate target process. They are also protected by OLLVM obfuscation with control-flow flattening enabled.
In September 2026, we discovered the Rust loader. It retrieves an encrypted payload from the C2 server, decrypts it, parses the PE header, and runs the Execute export function within its own process rather than injecting into another process. This in-process execution model eliminates the need for remote process manipulation.
OpsAgent main implantThe implant (version 5.2.8) rivals Cobalt Strike in functionality. It uses a worker-thread architecture: the main thread monitors connection health, while a worker thread processes commands from a queue. Three concepts structure its behavior:
- the worker thread (handles nearly all C2 commands)
- jobs (background tasks run in separate processes)
- links (connections to child agents used for lateral movement)
Exceptions include info, jobs, jobkill, worker_status, worker_restart, and exit, which execute immediately in the main thread.
OpsAgent can optionally obtain its C2 address by reading a public GitHub repository: hxxps://github[.]com/RonaldCMalcolm1983/staticPage. The address is stored in an encrypted form using AES‑CBC with the SHA‑256 hash of f4bb8c7e15d8b98d535eb20b09176b3d as the key and a zero initialization vector. The encrypted payload is wrapped with the markers GetConfig and EndConfig and then base64‑encoded.
Several commands — mimikatz_spawn, execute_assembly, pth_spawn, runpe, monitor start, and screenshot_service start — run background jobs in a separate process. To run a job, each creates a process and a named pipe, and receives shellcode from the C2 server. No command contains embedded mimikatz or PTH binaries. All payloads arrive remotely through the pipe, encrypted with XOR using key 604902af7b70b271. By default these commands use msiexec.exe as a host process, but the path can be changed. The exception is the monitor command, which uses notepad.exe for shellcode injection. This design keeps the implant small and lets operators deliver custom payloads remotely.
Injection commands support two modes: Legacy and DbgInjector. Legacy mode uses CreateProcessA and NtCreateThreadEx. DbgInjector creates a process in DEBUG state, allocates shared memory, sets a hardware breakpoint on FileTimeToSystemTime, then redirects RIP to the shellcode without creating a new thread.
Several code patterns suggest LLM-assisted development. For example, OpsAgent resolves WinAPI functions dynamically by hash: it calculates the hash of a function name, then searches for the matching address. Sometimes the plaintext name remains in memory before hashing. Additionally, all injection commands share near‑identical code structures, differing only in argument count and target process selection. This uniform approach matches LLM‑generated scaffolding.
Commands descriptionThe OpsAgent command set covers file system operations, process management, privilege escalation, shellcode injection, monitoring, and network pivoting. The C2 protocol runs over WebSocket with TLS and exchanges data in units called frames. Protocol frame types function as an extra command set enabling SOCKS proxy establishment, chunked file uploads, and inter-agent data forwarding. These frames are handled by a dedicated frame-handler function rather than the standard command decoder. The following combined table lists all text-based commands and protocol frame types together.
Several commands deserve closer attention. The monitor command manages keylogging through subcommands that start, stop, and configure logging threads. Screenshot features follow a similar design with session management subcommands. In contrast, the pivot subsystem uses a flatter command structure where each pivot command (pivot_list, pivot_start, pivot_stop, pivot_add, pivot_remove, pivot_auto) operates independently without nested subcommand hierarchies.
Some frame type numbers such as 0x20 appear unused in the current implementation. These may be traces of previous versions.
Type Identifier Description Command rm Removes a directory or a file Command ps Gets a process list Command drives Retrieves a list of drives Command ls Lists files in current or specified directory Command cat Returns the content of a file Command cd Sets current directory Command pwd Gets current directory Command run Runs an executable file Command shell Runs command in cmd.exe Command kill Terminates a specified process Command info Gets system information Command ps_icons Gets icons from a specified executable Command download Fetches a file from an infected machine Command exec Runs open in a shell with the specified path Command exit Stops OpsAgent running Command shinject Injects shellcode into a target process Command shspawn Creates a process and injects shellcode Command mimikatz_spawn Launches mimikatz via named pipe Command execute_assembly Runs .NET shellcode via injected loader Command pth_spawn Runs shellcode with pass-the-hash technique Command runpe Runs PE file inside another process Command make_token Creates token using username and password Command steal_token Steals token from another process Command rev2self Restores initial privilege of the process Command getuid Gets current user Command getsystem Attempts to obtain System-level privileges Command screenshot_sessions Lists screenshot sessions Command screenshot_service Manages screenshot sessions Command session_helper_status Shows status of all launched sessions Command monitor Manages keylogging threads Command link Connects agents via SMB Command unlink Disconnects from a child agent Command links Lists linked agents Command connect Connects agents via HTTP Command http_connect Connects agents via TCP Command pivot_list Lists pivot sessions Command pivot_start Starts pivot session Command pivot_stop Stops pivot session Command pivot_add Adds task to configuration file Command pivot_remove Removes task from configuration file Command pivot_auto Sets auto parameter for configuration items Command re_register Re-registers with C2 Command jobs Lists background jobs Command jobkill Terminates a specified job Command worker_restart Restarts stuck worker thread Command worker_status Returns worker thread status Frame type 0x00 Heartbeat Frame type 0x02 Acknowledge data Frame type 0x10 Process command Frame type 0x14 Cancel command Frame type 0x30 Start file upload Frame type 0x31 Upload file chunk Frame type 0x32 End upload Frame type 0x33 Cancel upload Frame type 0x40 Establish SOCKS connection Frame type 0x42 Send data via SOCKS Frame type 0x43 Close SOCKS connection Frame type 0x44 Control SOCKS connections Frame type 0x52 Forward frame to child agent Frame type 0x54 Close link connection Additional modules AV/EDR killer moduleThis module installs a driver disguised as Beijing Jiangmin Antivirus (KV series), utilizing the \KvCorePortX0 filter port for communication. Upon receiving the 0x1D command followed by a target filename, the driver terminates the corresponding process. Its target list covers nearly every major security product on the market.
Additionally, the driver carries a valid digital signature, which facilitates its initial execution.
The process kill list contains approximately 220 entries, including:
-
- Security products: MsMpEng, SecurityHealthService, avp, ekrn, ccSvcHst, fcag, eadrline
- Remote access tools: TeamViewer_Desktop, TeamViewer_Service, tv_w32, tv_x64
- Monitoring/logging: Sysmon, Sysmon64, splunkd, wazuh-agent
- Backup services: VeeamNFSSvc, AcronisAgent, MBAMService
- Database processes: sqlservr, mysqld, mongod, redis-server
This module encrypts files using either AES-CBC or ChaCha20 based on a command-line flag. Each file receives a unique encryption key produced by RtlGenRandom. A 12-byte array serves as the ChaCha20 nonce or expands to a 16-byte AES initialization vector. Key exchange relies on X25519 Diffie-Hellman with a static public key embedded in the binary. The module generates an ephemeral key pair per session and encrypts the file key with ChaCha20 using the shared secret.
Beyond file encryption, the module actively disrupts infrastructure by terminating database processes including SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, and Redis. It also stops backup services such as Veeam. The module removes shadow copies, empties the recycle bin, and wipes temporary folders. Furthermore, any file deletion overwrites content with random data before removing the entry, preventing forensic recovery.
After encryption, the module drops a ransom note. It formats the message as an audit log demanding payment through a Tor onion address. The note offers two options: pay the “Audit & Consulting fee” for a vulnerability report or face public data disclosure.
Finally, the module’s configuration parameters include file extensions to encrypt, directories and files to whitelist, processes and services to terminate, and shadow copy deletion flags.
OpsAgent-rs (Rust version)The Rust rewrite maintains functional parity with the C++ version while introducing new capabilities. OpsAgent-rs initially communicates with the C2 via HTTP POST requests to retrieve commands. There are special commands that change this behavior. After receiving an upgrade command, the implant establishes a persistent WebSocket connection over TLS for ongoing C2 communication instead of continuing to send POST requests. Additionally, command identifiers shifted from text names to numeric constants. New commands include interactive shells, directory creation, and sleep-interval changes.
Command mapping between versions shows most legacy commands have Rust equivalents. However, screenshot and monitor commands now consolidate into a unified identifier rather than relying on an extensive set of subcommands. The Rust version removes the entire pivot command set, eliminating pivoting task management functionality.
C2 acquisition in the Rust version changed significantly. The configuration contains a flag controlling whether the implant checks GitHub for new C2 addresses. It also stores markers indicating the beginning and end of the encrypted C2 string. The GitHub README page holds both the legacy C2 format and an additional base64-encoded blob specifically for OpsAgent-rs. The encryption scheme was reworked to use AES-GCM instead of AES-CBC. To derive the GCM key, the decryption flow computes HMAC-SHA256 of the secret key c2-framework-psk-salt-v1 against the configuration data blob, then applies a second HMAC with the salt c2-encryption-key\x01. The nonce is the first 12 bytes of the decrypted payload and the tag occupies the last 16 bytes.
InfrastructureThe implant uses AWS-generated CloudFront CDN subdomains as C2 endpoints. Because these domains operate on shared infrastructure, their underlying IP addresses cannot serve as reliable standalone IOCs.
Domain IP Added on GitHub First seen ASN d19v1tntmz2i98.cloudfront.net – Jan 29, 2026 Feb 21, 2026 – d35htktbyt7nxc.cloudfront.net – Aug 20, 2026 Sep 6, 2026 – – 157.20.104.111 Aug 19, 2026 Aug 24, 2026 AS 136557The GitHub repository stayed active throughout the campaign until November 2026. Commit history shows ongoing updates until September 29, 2026, when the actor deleted the legacy C2 domain from the repository. This suggests the actor maintains the infrastructure actively and rotates domains as needed.
In November 2026, the GitHub repository was removed. However, this does not mean the campaign is over, as the latest Rust implants found contained a configuration with the GitHub feature disabled.
VictimsAuditTeam targets organizations from different countries. We observed victims in China, the Philippines, Senegal, Italy, Finland, Hong Kong and Russia. And according to the group’s leak site, there are victims in Turkey, Thailand, Ukraine, Argentina, South Korea, Japan, and Spain. All identified victims belong to different industries.
AttributionWe attribute the OpsAgent campaign to AuditTeam with high confidence. The following evidence supports this assessment:
- Ransom note format and “Audit & Consulting fee” terminology unique to this group
- Tor-based leak site listing targeted organizations
- Operational philosophy distinguishing them from conventional ransomware groups through remediation reports
Open sources first identified AuditTeam in March 2026 via dbdigest.com. In June, DeXpose reported that AuditTeam claimed responsibility for attacking a Russian organization and listed it on its leak site. The group claims a mission to educate organizations about cybersecurity through exploitation and remediation reports. This tactical approach separates them from traditional ransomware operators.
ConclusionsAuditTeam frames extortion as a paid security audit — a distinctive model among ransomware groups. The C++ to Rust transition signals continued toolchain investment. New Rust commands cover interactive shells, WebSocket upgrades, and directory management.
The specialized modules reveal thorough operational preparation: the AV/EDR killer uses a signed Jiangmin driver to disable security products, and the cryptor module terminates database processes, encrypts files, and removes shadow copies. These tools let the group neutralize defenses and optionally destroy data.
CloudFront CDN subdomains complicate takedown and make IP-based blocking impractical because the IP space is shared with legitimate traffic. While the actor rotates infrastructure, the public GitHub repository enables C2 discovery and its removal disrupts the attack chain.
Custom malware frameworks are typically developed and maintained by APT groups with dedicated engineering resources. AuditTeam shows that a ransomware crew can build comparable tooling. This shift may be enabled by AI-assisted development tools lowering the barrier to creating functional, multi-module implant architectures.
Indicators of compromise File hashesStagers
d3e49dceb89a25f5da4ff0c42e996857
bd4c327ad208cb722ad25e43ea3f35fc
5d1425ab3dad1d2de053f69529d227e1
f0d5752054f6b7af1325ea340c4326d0
83768e994c6bb72d0b430b98a71ec8d6
Driver
109cdc24ccd4872a3e4bf6f2d4f3c3d4 # driver of a legitimate antivirus product
C:\ProgramData\Microsoft\Windows\Caches\syscache.dat
C:\Users\{username}\AppData\Local\Microsoft\Windows\Caches\syscache.dat
C:\Users\{username}\AppData\Local\Microsoft\CLR_v4.0\syscache.dat
{modulepath}\syscache.dat
{TempPath}\syscache.dat
C:\Users\Public\kv_dbg.log
C:\Windows\Sysnative\drivers\kvcore.sys
C:\Windows\System32\drivers\kvcore.sys
Domains and IPs
d19v1tntmz2i98[.]cloudfront[.]net
d35htktbyt7nxc[.]cloudfront[.]net
157.20.104[.]111
GitHub page with C2
hxxps://github[.]com/RonaldCMalcolm1983/staticPage
Attackers Compromise Microsoft's Agent Framework PyPI Package to Steal Cloud Credentials
Russian COLD RELIC Hackers Use Stolen Google Workspace Data to Breach Second U.S. Organization
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- …
- následující ›
- poslední »



