Malicious code in aws-sdk-v4 (npm)
The npm package aws-sdk-v4 impersonates the legitimate @aws-sdk/client-s3 package and contains malicious code that exfiltrates environment information and system details to an attacker-controlled Telegram bot. On first import, it collects sensitive environment variables including potential secrets and sends them encoded to a hardcoded Telegram chat. The package also exposes unrelated wallet functions, indicating deceptive intent. This affects version 3.650.0 of aws-sdk-v4.
AI Analysis
Technical Summary
The aws-sdk-v4 npm package is a malicious package impersonating the legitimate AWS SDK client for S3. When its index.js is required, it serializes process environment variables along with hostname, username, home directory, platform, and current working directory into a JSON string, base64-encodes this data, and sends it via a Telegram Bot API sendMessage request to a hardcoded bot token and chat ID. A temporary flag file prevents repeated transmissions. This exfiltration can leak sensitive secrets such as CI tokens, cloud credentials, and API keys present in the environment. Additionally, the package exposes wallet-related functions inconsistent with its advertised purpose, reinforcing its deceptive nature. The known affected version is 3.650.0.
Potential Impact
Sensitive environment information and secrets present during the package import are transmitted to an attacker-controlled Telegram channel, potentially compromising credentials and other confidential data. This can lead to unauthorized access or further compromise of systems relying on these secrets.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using the aws-sdk-v4 package version 3.650.0 from untrusted sources. Remove the package if installed and verify that no sensitive credentials were compromised. Use only official AWS SDK packages from trusted repositories. Monitor for any unauthorized access that could result from leaked secrets. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in aws-sdk-v4 (npm)
Description
The npm package aws-sdk-v4 impersonates the legitimate @aws-sdk/client-s3 package and contains malicious code that exfiltrates environment information and system details to an attacker-controlled Telegram bot. On first import, it collects sensitive environment variables including potential secrets and sends them encoded to a hardcoded Telegram chat. The package also exposes unrelated wallet functions, indicating deceptive intent. This affects version 3.650.0 of aws-sdk-v4.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The aws-sdk-v4 npm package is a malicious package impersonating the legitimate AWS SDK client for S3. When its index.js is required, it serializes process environment variables along with hostname, username, home directory, platform, and current working directory into a JSON string, base64-encodes this data, and sends it via a Telegram Bot API sendMessage request to a hardcoded bot token and chat ID. A temporary flag file prevents repeated transmissions. This exfiltration can leak sensitive secrets such as CI tokens, cloud credentials, and API keys present in the environment. Additionally, the package exposes wallet-related functions inconsistent with its advertised purpose, reinforcing its deceptive nature. The known affected version is 3.650.0.
Potential Impact
Sensitive environment information and secrets present during the package import are transmitted to an attacker-controlled Telegram channel, potentially compromising credentials and other confidential data. This can lead to unauthorized access or further compromise of systems relying on these secrets.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid using the aws-sdk-v4 package version 3.650.0 from untrusted sources. Remove the package if installed and verify that no sensitive credentials were compromised. Use only official AWS SDK packages from trusted repositories. Monitor for any unauthorized access that could result from leaked secrets. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13218
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a73852cbf8831d5394f04dc
Added to database: 08/05/2026, 18:47:08 UTC
Last enriched: 08/05/2026, 22:03:03 UTC
Last updated: 08/05/2026, 22:03:03 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.