@depup/aws-sdk__credential-provider-processnpm
@depup/aws-sdk__credential-provider-process is a confirmed malicious npm package (MAL-2026-13623) that steals credentials and exfiltrates sensitive data (malicious versions 3.972.59-depup.0, 3.972.62-depup.0, 3.972.63-depup.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @depup/aws-sdk__credential-provider-process (npm)
What this malware does
@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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @depup/aws-sdk__credential-provider-process (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @depup/aws-sdk__credential-provider-process across your stack and pipelines.
If you installed it — respond
@depup/aws-sdk__credential-provider-process 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 @depup/aws-sdk__credential-provider-process 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 @depup/aws-sdk__credential-provider-process 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @depup/aws-sdk__credential-provider-process-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.