Security Researcher Builds SAST Scanner for AI-Generated Code and Audits 3,800 Public Repositories
A developer has published AigisSAST, a console-based static application security testing tool designed specifically for code produced by AI assistants such as Cursor. The scanner, written in approximately 3,000 lines of pure Python without any external dependencies, parses code using AST rather than simple pattern matching to reduce false positives on strings that resemble secrets.
The researcher ran the tool against roughly 3,800 public repositories. The first round targeted 126 projects explicitly marked as AI-generated through files such as .cursorrules or CLAUDE.md. Subsequent rounds examined 49 large open-source platforms, 2,292 smaller projects including Telegram bots and VPN panels, 471 production bots handling real payments via Stars, CryptoBot and YooKassa, and finally 879 additional repositories scanned blindly.
Key findings included 16,378 high or critical alerts in the initial pass on the 471 live bots; after manual triage only about 30 proved to be genuine exposures. These comprised Telegram bot tokens, OpenAI and Google service-account keys, MongoDB and TiDB connection strings with embedded passwords, and full .env files containing Marzban and 3x-ui credentials. Ten secrets were present in the current working tree while 22 existed only in Git history.
The scanner implements 21 rules covering hardcoded tokens for Telegram, GitHub, AWS and Stripe, SQL and command injection via f-strings, unsafe use of pickle and eval, missing JWT signature verification, overly permissive CORS, debug mode left enabled, and database ports exposed on 0.0.0.0. Each finding is accompanied by a human-readable explanation, risk description and suggested remediation, with secrets automatically masked before display.
AigisSAST also offers an automatic fix mode that moves secrets into .env files, updates .gitignore, replaces random token generation with the secrets module, disables debug flags, and hardens Docker and YAML configurations. SQL injection and JWT issues are left untouched because safe fixes require application-specific logic.
The author stresses that the project deliberately avoids any active validation of discovered credentials. No tokens were tested against live services, and the scanner only reads publicly available code. The complete source code is released under the MIT license on GitHub, and the developer invites community feedback through issues and pull requests to further reduce false positives.
Related articles
Passwordless Kubernetes Image Pulling with Artifact Keeper via ServiceAccount Tokens
Kubernetes 1.34 and later enables kubelet to forward a pod's ServiceAccount token to an external image credential provider plugin, allowing the plugin to exchange it for short-lived read-only credentials from a compatible registry. Artifact Keeper, an open-source Rust-based OCI and package registry, implements an OIDC provider that validates these tokens and issues temporary credentials without requiring imagePullSecrets in manifests. The approach follows zero-trust principles by eliminating long-lived secrets that can leak across namespaces or clusters. A custom credential provider binary handles the token exchange, enforces audience restrictions, and redacts sensitive data from logs. The solution requires specific ClusterRole permissions for nodes, kubelet flags, and registry-side OIDC mappings that bind Kubernetes namespaces to read-only groups. Testing on kind 1.34.3 confirmed successful pulls for authorized ServiceAccounts and clear 401 errors for unauthorized ones when imagePullPolicy is set to Always.
Malicious Code Injected into LiteLLM Open Source AI Package via Supply Chain Attack
The open-source generative AI tool LiteLLM had malicious code inserted into its official distribution packages, enabling credential theft and remote code execution. The compromise affected version 1.107.0 released on October 21, 2026, and was delivered through legitimate channels in a classic software supply chain attack. Seven malicious wheel files were uploaded to PyPI, while official container images on Docker Hub and GitHub Container Registry were also tainted. Security firm JFrog discovered that the malware steals a wide range of secrets including cloud credentials, SSH private keys, browser-stored passwords, development tokens, and AI service API keys from LiteLLM's database. The code also supports execution of externally fetched payloads and abuses Python's startup mechanisms to run even when the application itself is not loaded. This marks the second supply chain incident involving the project in 2026, following a separate event in March.
GhostAction Campaign Compromises 790 GitHub Repositories via Malicious Workflows
Researchers from OpenSourceMalware have identified 790 publicly accessible GitHub repositories containing malicious workflows planted by the GhostAction campaign as of October 9. The campaign abuses trusted maintainer accounts to inject workflows that automatically exfiltrate secrets including AWS access keys and tokens for GitHub, GitLab, Google, Slack, SendGrid, OpenAI, Anthropic, and OpenRouter. Earlier counts by GitGuardian recorded 772 repositories between August 31 and September 30, though the datasets differ and are not cumulative. A separate wave on October 8 impacted 346 repositories linked to two maintainer accounts, including a project belonging to Uber. The malicious workflow runs on code pushes or manual triggers, scans repository files and full Git history for credentials, and sends findings in plaintext to attacker infrastructure. Removing the workflow file does not mitigate exposure, as successful executions already leak credentials and old commits may still contain secrets.
SberTech Launches Platform V Orchestrator for Security Services to Scan Software Before Corporate Deployment
SberTech has announced the launch of a new direction focused on analyzing the security of software prior to its integration into corporate infrastructures. The initiative is built around the company's own Laboratory for Software Verification and the technological platform Platform V Orchestrator for Security Services. This platform combines components for working with both built-in and external analysis tools, enabling checks of digital artifacts, control over software composition and changes, and detection of vulnerabilities, hidden threats, and defects in source code and repositories. SberTech aims to replace fragmented checks and manual result processing with a single managed process, allowing scaled verification without proportional team growth. The move responds to the adoption of hundreds of products from various vendors, widespread use of open-source components, and rising attacks on software supply chains. Primary customers include banks, industrial enterprises, telecom operators, energy companies, and the public sector. The solution is offered as a standalone product that supports on-premises deployment and operation in isolated environments such as private clouds and dedicated data processing contours.