carousel-controller-mixinnpm
Advisory published Updated
carousel-controller-mixin is a confirmed malicious npm package (MAL-2026-5856) that steals credentials and exfiltrates sensitive data (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in carousel-controller-mixin (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for carousel-controller-mixin (version 999.0.0).
If you installed it — respond
carousel-controller-mixin is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If carousel-controller-mixin was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks carousel-controller-mixin-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.