What to look out for today
Two themes that matter to many smaller organisations (including those using outsourced developers):
- Software supply-chain tampering: reports of malware activity tied to malicious npm packages and abuse of GitHub Actions workflows in a supply-chain attack.
- AI coding assistant/workspace trust risk: a recently patched issue in Amazon Q Developer where a malicious code repository could lead to unintended command execution and cloud credential theft if a developer trusted/opened the workspace.
Why this matters to smaller businesses
You don’t need a big in-house engineering team to be affected. If you use a web agency, an app developer, an MSP building automations, or anyone who deploys code to your cloud/accounting/booking systems, a compromised dependency or build pipeline can:
- Introduce backdoors into your website/app, leading to data loss or fraud.
- Expose cloud credentials that can be used to access email, files, customer data, or infrastructure.
- Cause business disruption when services must be taken offline to investigate and rebuild.
Warning signs
- Unexpected new “maintenance” releases or dependency updates pushed with urgency and little explanation.
- Build/deployment jobs (e.g., CI) suddenly running at unusual times or from unfamiliar accounts.
- New GitHub Actions/workflow changes that nobody can clearly justify.
- Unexpected prompts asking developers to “trust” a workspace/repository, or to enable extra integrations/tools.
- Unexplained new cloud access keys created, new users added, or permissions broadened.
How attackers may exploit the situation
- Malicious dependencies: attackers publish or update packages that look legitimate, hoping they are pulled into builds and deployed into production.
- CI/CD abuse: if workflows (like GitHub Actions) are modified or abused, attackers can run unwanted steps during build/deploy and access secrets.
- Repository “trust” traps: a developer opens a booby-trapped repo and approves prompts, allowing tooling to perform actions that can expose credentials or run unintended operations.
What to do today
- Tell developers/outsourced partners: do not “trust” unfamiliar repos/workspaces by default; treat unexpected trust prompts as a security event.
- Inventory who can deploy: confirm which people/suppliers can deploy code to your website/apps and who can access your cloud/admin consoles.
- Check secrets hygiene: ensure build/deploy secrets are stored in approved secret stores and are not shared via chat/email.
- Turn on alerting: enable alerts for new cloud keys, new admin users, and permission changes.
- Ask for evidence: if a supplier says “we updated dependencies”, ask what changed and how they verified it was safe.
Ask your IT provider
- Do we (or any supplier) use npm and GitHub Actions in systems connected to our business? If yes, what monitoring is in place for workflow changes and secret access?
- How do you approve and pin software dependencies, and how quickly can you roll back if a dependency is found to be malicious?
- Which accounts can access our cloud credentials, and are those credentials rotated and protected with MFA?
- If developers use AI coding assistants (e.g., Amazon Q Developer), what is the policy on opening/trusting external repositories and handling tool integrations?
- What’s the incident plan if a build pipeline is suspected to be compromised (containment, secret rotation, rebuild from clean sources)?
Patch watch - only one short paragraph, and only if relevant
Amazon has already patched the reported Amazon Q Developer issue (CVE-2026-12957). If your developers (or outsourced devs) use Amazon Q Developer, confirm they’ve updated and review any guidance around trusting workspaces/repositories and Model Context Protocol (MCP) tool configurations.
One action today
Message your developer/IT supplier today: require approval before trusting/opening any unfamiliar repo/workspace, and confirm alerts are enabled for new cloud keys/admin users and GitHub Actions workflow changes.
Related Actions On Cyber resource
CTA: Actions On Cyber “Supplier & MSP Security Questions” checklist (include CI/CD, secrets handling, and incident response for build pipeline compromise).
Sources
- Miasma Malware Targets npm Packages and GitHub Actions in Supply Chain Attack (The Hacker News)
- Amazon Q Developer Flaw Could Let Malicious Repos Run Code via MCP Configs (The Hacker News)
This brief is for general awareness and does not replace advice from your IT provider, legal adviser, insurer or incident response specialist.