Highnpm1 affected version

s3-lambda-dynamodb-cdk

s3-lambda-dynamodb-cdk has 1 version on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls s3-lambda-dynamodb-cdk.

s3-lambda-dynamodb-cdk@15.10.16

The incident that flagged it

High20 Jul 2026

GitHub Advisory malware sweep - 5-package AWS/CDK dependency-confusion cluster, `upjsma` 9-version 3-day burst, and 80-package `@gocortexio/npmgremlinbox-*` Cortex red-team validation kit swept 2026-07-20

On 2026-07-20 GitHub's Advisory Database retired 86 CWE-506 npm malware advisories in a single sweep. Highlights: a 5-package AWS/CDK dependency-confusion cluster (alb-lambda-cdk, s3-lambda-dynamodb-cdk, lambda-cloudwatch-cdk, iot-kfh-s3, lwc-slds-lbc) published within a 20-minute window on 2026-07-18 with high dep-confusion pins, upjsma (9 versions across 3 days), and the 80-package @gocortexio/npmgremlinbox-* red-team validation kit from the Palo Alto Networks Cortex ecosystem tooling org.

Versions named here: 15.10.16

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

s3-lambda-dynamodb-cdk is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If s3-lambda-dynamodb-cdk is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.