{"items":[{"id":"NVI-00009987","kind":"supply_chain_event","title":"Malicious code in @s4yhiitestpoc/r2-https-b (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-whjq-6xm5-ggvh"],"plain_summary":"GitHub lists this malware advisory for @s4yhiitestpoc/r2-https-b. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-b48d2d338fc20cd6a8d6e0cc049e310c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b48d2d338fc20cd6a8d6e0cc049e310c","url":"https://github.com/advisories/GHSA-whjq-6xm5-ggvh","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-whjq-6xm5-ggvh","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:53.250Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b48d2d338fc20cd6a8d6e0cc049e310c"],"technology":"@s4yhiitestpoc/r2-https-b","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (e89449bafb4f816bd8605f45cedf0fec8ec0cff9088007a7a38aaea0a9db91ec)\nOn npm install, postinstall.js automatically collects installer-side identifying data — hostname, username, home directory, non-internal network interface addresses, DNS servers, current working directory, install directory, and the value of npm_config_registry (which discloses the installer's internal/private npm registry URL) — and POSTs it as JSON over HTTPS to the hardcoded author endpoint collector.oob.s4yhii.com at path /_npm-poc/beacon. In parallel, the script performs a DNS lookup against a unique per-run subdomain under oob.s4yhii.com (dns.lookup of .db03o8lag74hsugsg2j091t8mfcf437h3.oob.s4yhii.com), providing an out-of-band DNS confirmation channel that works even when outbound HTTPS is blocked. The dual-channel beacon, the capture of internal registry configuration, and the fully automated install-time trigger match the fingerprint of a dependency-confusion probe. The package's self-description as a proof-of-concept does not change the behavior: installer-side host and internal-infrastructure data leaves the host to an attacker-controlled destination without opt-in.\n\n---","public_affected_ranges":["= 1.0.0"]}],"null_published_at":"2026-10-31T22:13:44.197Z","source_updated_at":"2026-10-12T06:31:25.000Z","source_disclosed_at":"2026-10-12T06:31:24.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:06:53.250Z"}],"next_cursor":null,"snapshot_revision":"42594"}