TIKTOUK Toolkit Exploits Exposed WordPress Backups for AWS & Email Secrets

A newly documented cyberthreat dubbed “TIKTOUK” is harvesting an alarming volume of credentials from exposed WordPress backups—many yielding access to cloud systems and corporate email services. The campaign combines probing, file collection, password recovery and script scanning in a toolkit designed to extract sensitive secrets at large scale. Researchers from LevelBlue warn this isn’t a fringe threat: thousands of sites appear compromised, leaving AWS keys, email passwords, API tokens and more ripe for misuse.

Inside the TIKTOUK Operation

The toolkit operates through multiple coordinated components: two built in Python, another crawler system in Go for Linux. They pull tasks from a central service, survey WordPress sites, and deliver collected findings—everything from server credentials to security keys—to a control panel. Researchers say this panel already holds roughly 50,000 valid server-side credentials tied to around 37,000 domains. Hundreds of AWS key pairs have been confirmed active. The toolkit’s reach extends beyond just static configuration files; it targets environment settings, repository configs, debug logs and database backups when they’re left exposed.

TIKTOUK’s discovery process starts with identifying a WordPress installation and then deploying REST-based batch probes designed to reveal backups or configuration files—especially those accidentally published or misconfigured. If certain REST requests are blocked or result in forbidden responses, the toolkit adaptively switches methods (e.g. multipart encoding) to access them. Leaked backups such as wp-config.php.bak or .env files often unlock database credentials, encryption keys, licenses and other secrets that should never be public.

From Encryption to Email and JavaScript

One of the toolkit’s modules targets popular WordPress SMTP plugins—WP Mail SMTP, Easy WP SMTP, FluentSMTP—and can extract plaintext credentials even when emails are supposedly secured. It does this using encryption keys or WP configuration data obtained from files made public by misconfigured servers. In one scenario, AWS secret keys were used to derive credentials for Amazon SES email accounts.

Another component crawls JavaScript files linked from the site, scouring for patterns or secrets tied to services like SendGrid, AWS, Amazon Bedrock, and Anthropic. This is especially dangerous because JavaScript often ends up in public or semi-public code, and credentials exposed here have powered breaches in past incidents.

Although LevelBlue mapped various request structures to known WordPress vulnerabilities (specifically CVE-2026-60137 and CVE-2026-63030), they did not document any confirmed exploit of those within a live production site during their investigation. Their lab results showed the toolkit’s behavior under controlled conditions, aligning with observed telemetry that suggests real usage.

How to Spot and Stop TIKTOUK

Defenders are advised to watch for unusual REST batch requests (especially those combining delete or paragraph-rendering operations), changes in request encoding methods, hits to exposed configuration or backup files, and unexpected outgoing reports from the site. Key indicators of compromise (IoCs) have also been shared—SHA-256 hashes for various components, file names like wp2s_poll.py or wp-config.php.bak, and IP addresses suspected of hosting command-and-control or payload providers.

WordPress versions prior to 6.9.5 (on 6.9.x) and before 7.0.2 on newer releases are specifically flagged as vulnerable for the batch-route technique. Ultimately, LevelBlue urges site operators to align HTTP logs, local file hashes, and configuration history to quickly validate any suspicion. Isolated signs like a vulnerable path or a single IoC aren’t proof alone; the context matters.

This operation is a stark reminder that backups aren’t “set and forget.” A stray .bak file, a debug run, or a legacy plugin can expose your secrets for good. Those defending WordPress sites must enforce least-privilege practices, rotate keys, and audit configurations regularly. Avoid storing sensitive data in web-accessible locations, monitor unusual REST API traffic, and update WordPress and plugins to patched versions.