Which versions of cami-design are malicious?

The following npm versions of cami-design are flagged malicious: 0.2.5. Treat any of these as compromised.

How do I remediate cami-design if I installed it?

cami-design 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 cami-design — how do I know if it already compromised me?

If cami-design 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.

Is cami-design part of a known attack campaign?

Yes — cami-design is associated with the IN-MAL-2026-004509 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 cami-design across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cami-design (version 0.2.5).

Malicious package

cami-designnpm

Advisory published May 24, 2026Updated May 26, 2026

cami-design is a confirmed malicious npm package (MAL-2026-4504) that steals credentials and exfiltrates sensitive data (malicious version 0.2.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cami-design (npm)

MAL-2026-4504

Immediate action

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

npm uninstall cami-design

What this malware does

On install, scripts/install.js invokes autoUpdate.install(), which writes a launchd agent to ~/Library/LaunchAgents/co.themobilefirst.cami-design.update.plist (scripts/auto-update.js) that runs npm install -g cami-design@latest --silent every 24 hours and is loaded immediately via launchctl load. The persisted agent fetches whatever version of the package is published as @latest at any future moment, with global install scope and no integrity verification. This establishes a long-lived remote code execution channel: any subsequent malicious publish (including via a compromised npm account) will be silently auto-installed system-wide on every machine that ever installed this version. The persistence is opt-out-only (an environment variable disables it) with no prompt at install time. A separate postinstall behavior symlinks bundled directories into ~/.claude/skills/ with.bak backups; this is the advertised function and not the basis for the block, but it also mutates a user-owned config directory silently.

Malicious versions

1 flagged

0.2.5

Indicators of compromise (SHA-256)

57ccc787b2437085a18ed05c52fc473d8c28162cbe3cbbaa04adaefa73389da1

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cami-design (version 0.2.5).
If you installed it — respond
cami-design 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 cami-design 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

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

Campaign

IN-MAL-2026-004509

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cami-design-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