{"items":[{"id":"NVI-00009626","kind":"supply_chain_event","title":"Malicious code in nested-lib (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-vhwg-xx2q-m28q"],"plain_summary":"GitHub lists this malware advisory for nested-lib, nested-lib, nested-lib. 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-14b7f47b21cc12660ee43044beda2bcc"],"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-14b7f47b21cc12660ee43044beda2bcc","url":"https://github.com/advisories/GHSA-vhwg-xx2q-m28q","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-vhwg-xx2q-m28q","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:53.250Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-14b7f47b21cc12660ee43044beda2bcc"],"technology":"nested-lib","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (0a0b849de5330a4a4984a855f83ce1638b17e459d359312319ff35dc0e02f928)\nThe package declares `scripts.postinstall = \"node beacon.cjs\"` and `index.js` also invokes `require('./beacon.cjs').fire()` at module load. `beacon.cjs` POSTs a JSON payload containing `os.hostname()`, `__dirname`, `process.cwd()`, and `process.version` over plain HTTP to the hardcoded bare-IP endpoint `http://185.158.107.175:8787/_ah/dc`. The destination is not a documented first-party service and the host identifiers are sent without any opt-in. `index.js` otherwise exports a Proxy that returns no-op functions for every property access, so the package provides no real functionality — its sole on-install and on-require effect is the beacon. The combination of a hollow Proxy shim, a bare-IP plain-HTTP destination, and automatic firing from both the npm lifecycle hook and the main module is consistent with a reconnaissance/confirmation beacon used to validate successful installation into target environments, typically preceding a second-stage payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebb","public_affected_ranges":["= 1.0.0"]},{"certainty":"source_listed","source_ids":["sr-14b7f47b21cc12660ee43044beda2bcc"],"technology":"nested-lib","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (0a0b849de5330a4a4984a855f83ce1638b17e459d359312319ff35dc0e02f928)\nThe package declares `scripts.postinstall = \"node beacon.cjs\"` and `index.js` also invokes `require('./beacon.cjs').fire()` at module load. `beacon.cjs` POSTs a JSON payload containing `os.hostname()`, `__dirname`, `process.cwd()`, and `process.version` over plain HTTP to the hardcoded bare-IP endpoint `http://185.158.107.175:8787/_ah/dc`. The destination is not a documented first-party service and the host identifiers are sent without any opt-in. `index.js` otherwise exports a Proxy that returns no-op functions for every property access, so the package provides no real functionality — its sole on-install and on-require effect is the beacon. The combination of a hollow Proxy shim, a bare-IP plain-HTTP destination, and automatic firing from both the npm lifecycle hook and the main module is consistent with a reconnaissance/confirmation beacon used to validate successful installation into target environments, typically preceding a second-stage payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebb","public_affected_ranges":["= 1.0.1"]},{"certainty":"source_listed","source_ids":["sr-14b7f47b21cc12660ee43044beda2bcc"],"technology":"nested-lib","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (0a0b849de5330a4a4984a855f83ce1638b17e459d359312319ff35dc0e02f928)\nThe package declares `scripts.postinstall = \"node beacon.cjs\"` and `index.js` also invokes `require('./beacon.cjs').fire()` at module load. `beacon.cjs` POSTs a JSON payload containing `os.hostname()`, `__dirname`, `process.cwd()`, and `process.version` over plain HTTP to the hardcoded bare-IP endpoint `http://185.158.107.175:8787/_ah/dc`. The destination is not a documented first-party service and the host identifiers are sent without any opt-in. `index.js` otherwise exports a Proxy that returns no-op functions for every property access, so the package provides no real functionality — its sole on-install and on-require effect is the beacon. The combination of a hollow Proxy shim, a bare-IP plain-HTTP destination, and automatic firing from both the npm lifecycle hook and the main module is consistent with a reconnaissance/confirmation beacon used to validate successful installation into target environments, typically preceding a second-stage payload.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebb","public_affected_ranges":["= 1.1.0"]}],"null_published_at":"2026-10-31T22:13:39.925Z","source_updated_at":"2026-10-11T15:31:23.000Z","source_disclosed_at":"2026-10-11T15:31:12.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"}