Armando found that db-evo v1.1.4, a database schema evolution and migration tool developed by art-ws.com, was maliciously modified on September 15, 2025 -- more than four years after its original publication. The injected version adds a postinstall hook that runs an AWS credential stealer, targeting developer and CI/CD environments that run npm install with AWS credentials in scope.
Key Findings
- Malicious version: v1.1.4, published 2025-09-15; v1.1.3 is clean
- Entry point: postinstall lifecycle hook fires automatically on npm install
- Targets: Node.js developer machines and CI/CD pipelines -- harvests AWS and cloud credentials
- Detection: Script-JS.Worm.SupplyChain, Text.Worm.SupplyChain, Archive-GZIP.Worm.SupplyChain, Archive-TAR.Worm.SupplyChain
Package Background
db-evo is a database schema evolution and migration package developed by art-ws.com, a software development company. The package was first published on February 11, 2021, with an active development history including multiple releases across its 1.0.x and 1.1.x lines. The publisher account (art-ws) manages 34 npm packages. The intel signal no-github-tag for v1.1.4 indicates the malicious version was published without a corresponding git tag in the repository, consistent with an unauthorized injection outside the normal release workflow.
The clean v1.1.3 was released on September 1, 2025. The malicious v1.1.4 and v1.1.5 appeared on September 15, 2025, two weeks later.
Attack Analysis
Armando's analysis shows that v1.1.4 introduces two changes to the clean v1.1.3: bundle.js is added, and package.json is modified to add a postinstall hook. The technique and payload are identical to other packages injected in the same wave.
bundle.js (sha256: dc67467a39b70d1cd4c1f7f7a459b35058163592f4a9e8fb4dffcbba98ef210c) is the same AWS credential-stealing payload confirmed across multiple packages in this campaign. It bundles the AWS SDK for JavaScript v3 with attacker code that resolves credentials from environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN), the AWS IMDS endpoint at 169.254.169.254, ECS task metadata at 169.254.170.2, GCP metadata at metadata.google.internal, and web identity token files. Collected credentials are exfiltrated to https://webhook.site/bb8ca5f6-4175-45d2-b042-fc9ebb8170b7.