spectral-core@3.0.6
Spectral analysis core utilities
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe build action performs direct collection and external transmission of environment, system, and cloud metadata. This is concrete installation-triggered data exfiltration, so the package should be blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package through a path that runs its node-gyp build action.
Impact
Installation can disclose environment data, network details, and available cloud metadata to an external recipient.
Mechanism
The action reads process environment data, gathers system network information, posts the data to webhook.site, and requests instance metadata for additional forwarding.
Attack narrative
The manifest enables gyp processing, and binding.gyp defines a Node action that reads environment and network data and sends it to a fixed webhook.site endpoint. The action also requests cloud instance metadata and forwards returned information to that endpoint.
AI rationale
The build action performs direct collection and external transmission of environment, system, and cloud metadata. This is concrete installation-triggered data exfiltration, so the package should be blocked.
Evidence
package.jsonbinding.gyp
Network endpoints3
webhook.site/d6092bdc-05c0-45da-a280-c343ea6d6156169.254.169.254/latest/user-data169.254.169.254/latest/meta-data/
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json sets gypfile to true, and binding.gyp defines a Node action that reads process environment data.
- The action posts collected environment and system details to webhook.site and retrieves cloud instance metadata for forwarding to the same destination.
Evidence against
Behavioral surface
Source & flagged code
9 flaggedCTF_HANDOFF_CURSE_DEPENDENT_v2.mdView file
20patternName = npm_token
severity = critical
line = 20
Critical
Critical Secret
Package contains a critical-looking secret pattern.
CTF_HANDOFF_CURSE_DEPENDENT_v2.mdView on unpkg · L2020patternName = npm_token
severity = critical
line = 20
Critical
Secret Pattern
npm access token in CTF_HANDOFF_CURSE_DEPENDENT_v2.md
CTF_HANDOFF_CURSE_DEPENDENT_v2.mdView on unpkg · L20100patternName = aws_access_key
severity = critical
line = 100
Critical
Secret Pattern
AWS access key ID in CTF_HANDOFF_CURSE_DEPENDENT_v2.md
CTF_HANDOFF_CURSE_DEPENDENT_v2.mdView on unpkg · L100binding.gypView file
Findings
4 Critical4 High1 Medium
CriticalCritical SecretCTF_HANDOFF_CURSE_DEPENDENT_v2.md
CriticalManifest Confusionpackage.json
CriticalSecret PatternCTF_HANDOFF_CURSE_DEPENDENT_v2.md
CriticalSecret PatternCTF_HANDOFF_CURSE_DEPENDENT_v2.md
HighAi Review Evidencepackage.json
HighAi Review Evidencebinding.gyp
HighAi Review Evidencebinding.gyp
HighAi Review Evidencebinding.gyp
MediumShips Build Helperbinding.gyp
Affected versions and remediation
This report applies to spectral-core@3.0.6.
See all versions of spectral-core for other recorded verdicts.
- Avoid installing spectral-core@3.0.6. 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.