spectral-core@3.0.2
Spectral analysis core utilities
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package’s native build action performs unconsented collection and remote transmission of local data. This is concrete malicious behavior and warrants blocking publication.
Decision evidence
public snapshot- The manifest enables native build handling with `gypfile: true`.
- The build action runs Node code that reads `/flag.txt` and falls back to matching files or environment data, then writes the result to `/app/static/FINAL_FLAG.txt`.
- The action POSTs the collected data to a fixed `webhook.site` endpoint.
Source & flagged code
6 flaggedThe build action runs Node code that reads `/flag.txt` and falls back to matching files or environment data, then writes the result to `/app/static/FINAL_FLAG.txt`.
binding.gypView on unpkg · L1The build action runs Node code that reads `/flag.txt` and falls back to matching files or environment data, then writes the result to `/app/static/FINAL_FLAG.txt`.
binding.gypView on unpkg · L1The action POSTs the collected data to a fixed `webhook.site` endpoint.
binding.gypView on unpkg · L1Findings
Affected versions and remediation
This report applies to spectral-core@3.0.2.
See all versions of spectral-core for other recorded verdicts.
- Avoid installing spectral-core@3.0.2. 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.