Which versions of carousel-controller-mixin are malicious?

The following npm versions of carousel-controller-mixin are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate carousel-controller-mixin if I installed it?

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.

I already installed carousel-controller-mixin — how do I know if it already compromised me?

If carousel-controller-mixin was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is carousel-controller-mixin part of a known attack campaign?

Yes — carousel-controller-mixin is associated with the IN-MAL-2026-006741, GHSA-cm93-hx95-m69r campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find carousel-controller-mixin across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for carousel-controller-mixin (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging carousel-controller-mixin across your stack and pipelines.

Malicious package

carousel-controller-mixinnpm

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)

MAL-2026-5856

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall carousel-controller-mixin

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

1 flagged

999.0.0

Indicators of compromise (SHA-256)

c1a4b1be297682ca77d8a92fc502887ee6d718a5541fa88413acdc6accb3ed97

f91353de7458768895b5ef059ccf6a93e994e1af38203ec719a810898f02a835

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for carousel-controller-mixin (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging carousel-controller-mixin across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks carousel-controller-mixin before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. carousel-controller-mixin on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006741GHSA-cm93-hx95-m69r

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database