Which versions of aws-sdk-v4 are malicious?

The following npm versions of aws-sdk-v4 are flagged malicious: 3.650.0. Treat any of these as compromised.

How do I remediate aws-sdk-v4 if I installed it?

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

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

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

Malicious package

aws-sdk-v4npm

aws-sdk-v4 is a confirmed malicious npm package (MAL-2026-13218) that steals credentials and exfiltrates sensitive data (malicious version 3.650.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aws-sdk-v4 (npm)

MAL-2026-13218

Immediate action

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

npm uninstall aws-sdk-v4

What this malware does

Package aws-sdk-v4 impersonates @aws-sdk/client-s3 and, on require() of index.js, JSON-stringifies process.env together with hostname, username, home directory, platform, and current working directory, base64-encodes the blob, and sends it as a Telegram Bot API sendMessage request to a hardcoded bot token and chat_id 8969499041 at api.telegram.org. A temporary flag file gates repeat executions. Any secrets present in the installer's environment (CI tokens, cloud credentials, API keys) are transmitted to the attacker on first import. The package additionally exposes wallet-shaped functions (createWallet, signTransaction, generateMnemonic) inconsistent with its advertised AWS SDK purpose, reinforcing the deceptive-naming delivery vector.

Malicious versions

1 flagged

3.650.0

Indicators of compromise (SHA-256)

3753967ef5752d68dd0880c092d77ab42bb18fe5e081c258961572581cb81aa7

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

Campaign

IN-MAL-2026-015733

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aws-sdk-v4-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