spectral-core@3.0.7
Spectral analysis core utilities
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest enables npm's implicit native build behavior, and the build action retrieves AWS container credentials and metadata before POSTing them to a fixed external endpoint. This is concrete installation-triggered credential disclosure, so the package should be blocked.
Decision evidence
public snapshot- The manifest sets `gypfile` to true, enabling npm's implicit node-gyp install behavior.
- `binding.gyp` defines a Node action that runs during the build.
- The action sends POST requests to a fixed webhook.site URL.
- It reads the AWS container credential endpoint and posts its response as `CREDS`.
- It also reads ECS task metadata and posts those responses.
Source & flagged code
7 flagged`binding.gyp` defines a Node action that runs during the build.
binding.gypView on unpkg · L4The action sends POST requests to a fixed webhook.site URL.
binding.gypView on unpkg · L12Findings
Affected versions and remediation
This report applies to spectral-core@3.0.7.
See all versions of spectral-core for other recorded verdicts.
- Avoid installing spectral-core@3.0.7. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.