xssdoctor-muse-task448-provider-runtime: malicious npm package exfiltrates local canary file to hardcoded host
Severity: critical · Patch status: no-fix-needed · Since 2026-11-20
The npm package xssdoctor-muse-task448-provider-runtime version 1.0.0 is malicious, according to a GitHub Advisory Database entry sourced from Amazon Inspector. Its exported runProviderHealth() reads ../../../canary/.task318-private-canary relative to the package install location, base64url-encodes the contents, and sends them as a query parameter to the hardcoded endpoint https://poc.xssdoctor.com/task328/collect. The scoped-looking package name is consistent with a dependency-confusion lure: an internal build resolving this public name instead of a private dependency could load it and transmit any file present at that path to the author-controlled host. The read reaches outside the package directory and the destination is not caller-configurable. No patched versions exist; affected users must remove the package and treat exposed canary contents as compromised.
What to do
- Immediately remove or block xssdoctor-muse-task448-provider-runtime@1.0.0 from all npm builds, lockfiles, caches, and developer machines; do not load the module.
- Block and monitor egress to poc.xssdoctor.com and inspect proxy, DNS, and firewall logs for requests to /task328/collect.
- Audit dependency resolution and lockfiles for dependency-confusion exposure, especially any internal package with a similar scoped-looking name.
- If the package may have executed, treat ../../../canary/.task318-private-canary and adjacent secrets as exposed; rotate credentials and review access logs.
- Search source and build logs for runProviderHealth() calls and add npm malware/allowlist controls.
Sources
All live incidents on Threat Watch