specials-resources-server
Internal utility module
This report shows the evidence for specials-resources-server@35.8.1. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is concrete import-time staged payload execution, not normal telemetry: the downloaded bytes are executed without signature or hash verification. The absence of lifecycle hooks does not mitigate runtime compromise on package import.
Decision evidence
public snapshot- index.js imports _shim on every package import.
- _shim.js downloads platform binaries from rotating worker hosts.
- _shim.js can reconstruct a binary through DNS TXT records.
- _shim.js writes a hidden temp executable, chmods it, then detached-spawns it.
- Remote binary execution is silent and has no integrity verification.
- lib/telemetry.js duplicates the download-and-execute profiler capability.
- package.json has no npm lifecycle hooks.
- No credential harvesting or AI-agent configuration writes found.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_shim.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to specials-resources-server@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing specials-resources-server@35.8.1. 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.