race-condition-exploit
Audited by Socket on Apr 22, 2026
4 alerts found:
SecurityMalwarex3High-risk offensive exploit skill. It is internally consistent with its stated exploit purpose, but that purpose gives an AI agent concrete instructions to attack live systems, including financial abuse, rate-limit bypass, workflow hijacking, and webshell timing. No strong evidence of credential theft or obfuscation, but the operational risk is high because the skill directly enables unauthorized exploitation.
This fragment is overwhelmingly offensive: it includes (a) a concrete symlink-race privilege/escalation persistence attempt targeting a cron directory and (b) multiple concurrency-driven PoCs for abusing multi-step race conditions in financial/commerce/voting business logic (double-spend, coupon reuse, inventory oversell, vote inflation). In a software supply-chain context, this is a high-risk malicious/abusive payload category rather than a benign dependency. Recommend treating the package as malicious/untrusted and isolating it; do not install or execute.
This module is an offensive exploitation toolkit for web race-condition/state-machine vulnerabilities and related authentication/authorization timing abuses. It actively crafts and synchronizes sensitive requests (password reset, email change, 2FA verification), performs high-concurrency bursts for rate-limit/OTP bypass, and attempts token/2FA reuse before invalidation. It also includes an attack-biased HTTP/2 client approach (single-write frame packing) and disables TLS verification in the example client. No clear benign/defensive purpose is evident, so it should be treated as high-risk and unsuitable for inclusion in legitimate software supply chains.
This code is intentionally malicious/offensive: it automates exploitation of race conditions to cause duplicate state changes (double-spend/duplicate redemption), deploys a PHP webshell enabling remote command execution, and automates exfiltration of sensitive files. Treat as exploit tooling/backdoor; do not run against systems unless under an explicit, authorized engagement. If found in a codebase unexpectedly, remove and investigate source of inclusion and any credential exposure.