# MAL-2026-5856: Malicious code in carousel-controller-mixin (npm)


- **Type:** Malicious package
- **Package:** `carousel-controller-mixin` (npm)
- **Published:** 16 Jun 2026
- **Also known as:** GHSA-cm93-hx95-m69r

## What is MAL-2026-5856?

MAL-2026-5856 is a malicious package in carousel-controller-mixin, published on 16 Jun 2026. 

### Official description

package.json declares both preinstall and postinstall hooks that execute callback.js on every install. callback.js collects username, uid, hostname, cwd, homedir, local and external IPs (via https.get to api.ipify.org) and probes for CI/cloud credential environment variables (AWS_ACCESS_KEY_ID, GITHUB_TOKEN, NPM_TOKEN, DOCKER_PASSWORD) along with GITHUB_REPOSITORY/GITHUB_ACTOR/BUILD_NUMBER context. The collected data is POSTed to a hardcoded Discord webhook (discord.com/api/webhooks/1516163806559076442/<redacted>) and additionally exfiltrated through a DNS side-channel: base64-encoded host data is prepended as a subdomain and resolved via dns.resolve() to defeat egress HTTP filtering on CI networks. Self-labeled as a dependency-confusion PoC, the version number 999.0.0 is the canonical floating-version bait used to win internal-name resolution. Harmful to any installer regardless of the 'research' framing.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-5856?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5856 is a malicious package: carousel-controller-mixin (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5856/ (Markdown: https://insights.sbomify.com/MAL-2026-5856/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5856

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5856/
Summaries are generated and may contain mistakes; the official description above is the record.