Malicious code in ledgerflow-deploy-utils (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5f0097d19be676ac30ff79dffcff38f128873c80115a8a150c3eceff0422aa93) On npm install, the package's postinstall script queries the AWS instance metadata service (IMDSv1) at 169.254.169.254 for the attached IAM role and POSTs the result, along with an IMDS-reachability probe, over plain HTTP to a hardcoded bare IP (54.226.194.239:80/chain3). The published library surface (index.js) only exports two no-op console.log stubs named validate/deploy, with no real functionality — the entire effective behavior is the install-time reconnaissance against AWS-hosted installers and CI runners. The combination of a placeholder API, a generic deployment-utility name suggesting an internal/private package, and install-time recon to a hardcoded bare-IP C2 matches the dependency-confusion / internal-name-squat pattern targeting corporate build systems, where exposed IAM role names enable follow-on credential abuse against the installer's cloud environment.
AI Analysis
Technical Summary
The ledgerflow-deploy-utils npm package (version 1.0.1) includes a postinstall script that accesses the AWS instance metadata service at 169.254.169.254 to obtain IAM role credentials. It then transmits these credentials and a reachability probe to a hardcoded IP address (54.226.194.239) over plain HTTP. The package exports only placeholder functions with no real functionality, indicating the main intent is to perform install-time reconnaissance on AWS-hosted environments. This technique is consistent with dependency confusion or internal name squatting attacks aimed at stealing cloud credentials from corporate build systems and CI runners.
Potential Impact
If installed in an AWS-hosted environment, this package can leak IAM role credentials to an attacker-controlled server. This exposure enables potential follow-on credential abuse, including unauthorized access to cloud resources. The malicious behavior occurs silently during installation, making detection difficult. No direct exploit in the wild is currently known, but the impact of credential theft is high.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing ledgerflow-deploy-utils version 1.0.1. Review and restrict usage of internal or private npm packages to prevent dependency confusion attacks. Monitor for unexpected network connections to suspicious IP addresses during package installation. Check vendor advisories or npm security advisories for updates or removal of the malicious package. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in ledgerflow-deploy-utils (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5f0097d19be676ac30ff79dffcff38f128873c80115a8a150c3eceff0422aa93) On npm install, the package's postinstall script queries the AWS instance metadata service (IMDSv1) at 169.254.169.254 for the attached IAM role and POSTs the result, along with an IMDS-reachability probe, over plain HTTP to a hardcoded bare IP (54.226.194.239:80/chain3). The published library surface (index.js) only exports two no-op console.log stubs named validate/deploy, with no real functionality — the entire effective behavior is the install-time reconnaissance against AWS-hosted installers and CI runners. The combination of a placeholder API, a generic deployment-utility name suggesting an internal/private package, and install-time recon to a hardcoded bare-IP C2 matches the dependency-confusion / internal-name-squat pattern targeting corporate build systems, where exposed IAM role names enable follow-on credential abuse against the installer's cloud environment.
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 ledgerflow-deploy-utils npm package (version 1.0.1) includes a postinstall script that accesses the AWS instance metadata service at 169.254.169.254 to obtain IAM role credentials. It then transmits these credentials and a reachability probe to a hardcoded IP address (54.226.194.239) over plain HTTP. The package exports only placeholder functions with no real functionality, indicating the main intent is to perform install-time reconnaissance on AWS-hosted environments. This technique is consistent with dependency confusion or internal name squatting attacks aimed at stealing cloud credentials from corporate build systems and CI runners.
Potential Impact
If installed in an AWS-hosted environment, this package can leak IAM role credentials to an attacker-controlled server. This exposure enables potential follow-on credential abuse, including unauthorized access to cloud resources. The malicious behavior occurs silently during installation, making detection difficult. No direct exploit in the wild is currently known, but the impact of credential theft is high.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing ledgerflow-deploy-utils version 1.0.1. Review and restrict usage of internal or private npm packages to prevent dependency confusion attacks. Monitor for unexpected network connections to suspicious IP addresses during package installation. Check vendor advisories or npm security advisories for updates or removal of the malicious package. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6591
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed6d27e9c79719938eb9
Added to database: 06/29/2026, 22:10:53 UTC
Last enriched: 07/10/2026, 12:06:22 UTC
Last updated: 07/28/2026, 04:09:11 UTC
Views: 26
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.
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.