Which versions of concierge-sdk are malicious?

The following npm versions of concierge-sdk are flagged malicious: 99.99.99, 99.99.100, 99.99.101. Treat any of these as compromised.

How do I remediate concierge-sdk if I installed it?

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

If concierge-sdk 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 concierge-sdk part of a known attack campaign?

Yes — concierge-sdk is associated with the IN-MAL-2026-020020, IN-MAL-2026-020026, IN-MAL-2026-020027 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 concierge-sdk 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 concierge-sdk (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging concierge-sdk across your stack and pipelines.

Malicious package

concierge-sdknpm

concierge-sdk is a confirmed malicious npm package (MAL-2026-16145) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.99, 99.99.100, 99.99.101). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in concierge-sdk (npm)

MAL-2026-16145

Immediate action

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

npm uninstall concierge-sdk

What this malware does

The package's declared postinstall script executes exfil_v2.js at npm install time. That script harvests the full process environment, current working directory, and config/secret files (.env, secrets.json, /etc/environment, /etc/profile, workflow files, git-history secret matches), curls the Azure Instance Metadata Service at 169.254.169.254 to obtain a managed-identity access token for vault.azure.net and lists Key Vault secrets with it, and uses the runner's GITHUB_TOKEN against api.github.com to read repository secrets and Actions artifacts. All collected data is POSTed to a hardcoded webhook.site endpoint. A sibling exfil.js duplicates full process.env exfiltration to the same webhook.site collector under User-Agent continental-sdk/1.0.

Malicious versions

3 flagged

99.99.9999.99.10099.99.101

Indicators of compromise (SHA-256)

63196bb3ca7cbb7e065a9cff120941ff3c3558c86ed1d40d6334384d4ce0a94c

4de458111994244a0a590117185f9e345ff27043c129d4ea24fcb3be5f98f67b

66484d698cb071edcee1b1fff6236fd881a151ef065c450e8bdee218c48fe3a9

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 concierge-sdk (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging concierge-sdk across your stack and pipelines.
If you installed it — respond
concierge-sdk 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 concierge-sdk 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 concierge-sdk 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. concierge-sdk on npm has been identified as a malicious package (versions 99.99.99, 99.99.100, 99.99.101 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020020IN-MAL-2026-020026IN-MAL-2026-020027

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks concierge-sdk-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