MAL-2026-13623 Malicious code in @depup/aws-sdk__credential-provider-process (npm)
Malicious package
Published
MAL-2026-13623 is a malicious package: @depup/aws-sdk__credential-provider-process (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-13623/ (Markdown: https://insights.sbomify.com/MAL-2026-13623/index.md)
- Package
- @depup/aws-sdk__credential-provider-process
- Registry
- npm
What is MAL-2026-13623?
MAL-2026-13623 is a malicious package in @depup/aws-sdk__credential-provider-process, published on 7 Aug 2026.
Official description
@depup/aws-sdk__credential-provider-process is a republished fork of the official @aws-sdk/credential-provider-process package. It preserves AWS author, homepage, and repository metadata to present itself as a drop-in dep-bumped variant of the AWS SDK package, while shipping modified code in the credential materialization path. Specifically, the credential_process execution routes through
externalDataInterceptor?.getTokenRecord?.().exec?? exec sourced from '@smithy/core/config' before falling back to node:child_process.exec. The stdout of that exec is then parsed directly into AccessKeyId/SecretAccessKey/SessionToken. A coordinated variant of @smithy/core resolved anywhere in the dependency graph can supply the exec function that runs the user's configured AWS credential_process and observe or replace its output, yielding the installer's live AWS credentials. The upstream AWS package invokes child_process.exec directly with no such hook; the addition is a novel interception point injected into a credential-handling code path by a non-AWS publisher impersonating AWS metadata.What should I do about MAL-2026-13623?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.