spectral-core
Affected
- Versions:
3.0.10,3.0.11,3.0.12,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6,3.0.7,3.0.9
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in spectral-core (npm)
spectral-core contains no library code: where an index.js is present (e.g. 3.0.12) it only exports the package name and version. It ships a binding.gyp (and package.json sets "gypfile": true), so npm runs node-gyp rebuild on install, and the binding.gyp declares a build action ("Finalizing spectral-core setup") that runs inline JavaScript with node -e. Versions 3.0.3 to 3.0.12 (3.0.8 was never published) were published on 2026-10-28 between 19:42 and 21:24 UTC, each with a different collection script. Depending on the version, the script:
/proc/1/environ; 3.0.4, 3.0.6) and of its own process (/proc/self/environ; 3.0.6), greps the environment for htb and flag (3.0.4), and enumerates process.env with Object.entries (3.0.11, 3.0.12);*flag* or *HTB* and for files containing HTB{, and prints the first lines of /run/secrets/* (3.0.3); recursively lists /var/run/secrets (3.0.5); reads /flag.txt (3.0.9);AWS_CONTAINER_CREDENTIALS_RELATIVE_URI and the ECS container metadata URI variable (3.0.7), and fetches the ECS task metadata endpoint ($ECS_CONTAINER_METADATA_URI/task) with curl and posts the result (3.0.11);/fetch.sh, /run_test.sh and /setup_test.sh (3.0.5) and /opt/ph/sitecustomize.py (3.0.12), lists /scripts (3.0.10) and /opt (3.0.11), and collects /etc/resolv.conf, ip neigh and ip route output (3.0.6);/d6092bdc-05c0-45da-a280-c343ea6d6156 in 3.0.7, /f604623f-fc78-4447-9225-6772f7f12cb1 in 3.0.9 to 3.0.12). In 3.0.3 to 3.0.6 the destination is outside the scanned excerpt, but each version loads https and a full-file static rule for webhook/collection services matched.Version 3.0.6 also shipped a file named CTF_HANDOFF_CURSE_DEPENDENT_v2.md, and the strings searched for suggest the author was targeting a capture-the-flag environment. The script nevertheless runs on any machine where npm builds the package's binding.gyp during install, collects (depending on the version) environment variables, secret files, local scripts and ECS task metadata, and sends data to a third-party endpoint (webhook.site where the destination is visible). The same webhook.site endpoint /f604623f-... is used by @dmangal/[email protected]. All 2026 versions (0.0.0-stage and 3.0.1 to 3.0.12) were unpublished on 2026-10-28 at 22:29 UTC.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (451c36f03e81be0ff6c85334587d7ff401de1e5134e179557ec4bc454cd7ba76)
The tarball ships only package.json and binding.gyp (plus a markdown file), with gypfile: true set in package.json so npm invokes node-gyp rebuild on install. binding.gyp declares a 'none'-type target with no native source files; its sole purpose is an inline action that runs node -e with an embedded script. At install time that script reads /proc/1/environ and /proc/self/environ (container/pod entrypoint environment variables, which routinely contain CI/CD secrets and cloud credentials), collects DNS/socket/ARP/route reconnaissance output, queries the AWS EC2 instance metadata service at 169.254.169.254 for user-data and meta-data, and POSTs the collected data to the hardcoded collector https://webhook.site/d6092bdc-05c0-45da-a280-c343ea6d6156. The package exposes no library functionality — main: index.js is declared but index.js is not shipped — so the binding.gyp exists solely as a vehicle for install-time code execution and credential exfiltration. The name resembles the legitimate @stoplight/spectral-core project but the shipped contents are unrelated to it.
Not rated by the source.
3.0.10, 3.0.11, 3.0.12, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0.7, 3.0.9None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0