GitHub Repo Trap with 1774 Stars Mimics Microsoft Activation Scripts to Deliver Malware via Telegram Bot
A Telegram bot that surfaces daily trending GitHub repositories exposed a sophisticated supply-chain trap disguised as the legitimate Microsoft Activation Scripts project.
The repository appeared in the bot’s feed on 26 September with 1774 stars, a clean description and matching tags. Its single README file contained an installation command written in reversed form: iex(irm(-join"…"[-1..-99])). PowerShell reversed the string at runtime, fetched a script from a lookalike domain and executed it immediately, bypassing both human review and simple link scanners.
The attacker’s account had been created only 94 seconds before the repository. The command mimicked the real one-liner used by genuine Microsoft Activation Scripts, increasing the chance that developers would paste it directly into a terminal.
Why obvious filters fail
Scanning 321 repositories sent by the bot between 15 July and 8 October showed that blocking any irm|iex pattern from non-GitHub domains would hide 38 legitimate projects, including codex and opencode, as well as installers for rustup and uv. Checking only account age also failed: on the day the trap appeared the account was already 34 days old.
Two independent signals proved effective. The first normalizes README text, removes invisible characters and backticks, then detects masked execution via reversed strings, base64, mshta, certutil, bitsadmin or -WindowStyle Hidden. The second flags one-time owners created less than 30 days before the repository when the repository contains less than 10 KB or only README and LICENSE files.
Both rules triggered exclusively on the malicious activator and were deployed on 9 October. The bot now replaces flagged repositories, explains the reason and removes the summary button.
Preventing LLM hallucinations
The same pipeline uses DeepSeek to generate one-sentence Russian summaries. A groundedness check adapted from the open-source KKKKhazix/AIHOT project rejects any Latin-capitalized word, number over two digits or percentage absent from the source text. After tuning, the filter reduced false rejections to five cases out of 303 summaries while catching real fabrications such as references to Ruby, Cypress and Scratch.
Related articles
GhostAction Campaign Expands to Inject Malicious GitHub Workflows Stealing AWS Keys and Tokens
The GhostAction campaign has returned with an expanded technique that targets a wider range of credentials across hundreds of repositories. On October 8, two compromised maintainer accounts injected a malicious workflow named security-audit.yml into 346 GitHub repositories, including high-profile projects such as uber/athenadriver and kitao/pyxel. The workflow disguises itself as a security audit routine and executes automatically on every code push, exfiltrating credentials via HTTP requests to attacker-controlled servers. Unlike previous waves that only harvested GitHub Actions secrets, the new version also scans the working directory and full git history for forgotten credentials in older commits. Targeted data includes AWS access keys, GitHub and GitLab tokens, Google API keys, Slack and SendGrid tokens, OpenAI and Anthropic credentials, PyPI passwords, and crates.io tokens. Since October 7, more than 500 GitHub accounts have planted similar workflows, building on earlier campaigns that affected 817 repositories in September 2025 and 772 between August and September.
Security Researcher Builds SAST Scanner for AI-Generated Code and Audits 3,800 Public Repositories
A developer released AigisSAST, a lightweight open-source static analysis tool written in pure Python with no external dependencies, specifically tuned to detect common mistakes made by AI coding assistants. The scanner was run across roughly 3,800 repositories ranging from small pet projects to popular open-source platforms. It identified thousands of potential secrets and misconfigurations, yet manual review reduced the number of genuine leaks to approximately 30 cases, mostly Telegram bot tokens, database credentials, and committed .env files. The project also examined 471 production-grade Telegram bots handling payments and VPN services, uncovering 31 repositories that exposed real credentials either in current code or in Git history. AigisSAST includes 21 detection rules, 193 regression tests, automatic remediation via the fix command, and seamless integration with GitHub Actions. The author deliberately avoided validating any discovered keys to stay within ethical research boundaries.
Vendor Responsibility in Open Source: Licensing Obligations Exposed by Sonatype Nexus Changes
The article examines how vendors building products on copyleft open source projects like Nexus Repository OSS inherit significant legal and security responsibilities under licenses such as EPL 1.0. Sonatype's February 2025 shift from regular OSS binary releases to a limited Community Edition forces downstream vendors to handle their own builds, patch porting, and compliance disclosures. This change highlights the second part of copyleft licenses that outlines obligations for distributors, including revealing modifications and assuming liability for the final product. Security implications arise because critical vulnerabilities in the upstream project must now be tracked and patched by the vendor, with delays creating measurable supply chain risks. The piece provides a practical checklist for buyers to assess licensing hygiene, SBOM availability, and vulnerability response times in any open source-based solution.
PhantomSub Campaign Deploys 101 Malicious npm Packages to Hijack WhatsApp Accounts for Unauthorized Channel Subscriptions
Researchers at OX Security uncovered 101 malicious npm packages tied to the PhantomSub campaign that abuse connected WhatsApp accounts to subscribe users to promotional channels without consent. The packages disguise themselves as modified versions of the open-source Baileys library used for WhatsApp automation. Attackers rely on authenticated sessions rather than simple package installation, allowing them to control subscriptions through lists stored on GitHub, in plaintext, or as encoded identifiers. The packages have accumulated roughly 490,000 downloads, including 116,000 in the past 30 days, though the exact number of compromised accounts remains unknown. As of 28 September, npm had removed only 16 of the identified packages. The operation ultimately benefits channels selling bots, game resources, accounts, and promotion services by inflating subscriber counts while disabling notifications to hide the activity.