{"items":[{"id":"NVI-00009735","kind":"supply_chain_event","title":"Malicious code in another-very-long-name (npm)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-9w99-w8fq-2x8w"],"plain_summary":"GitHub lists this malware advisory for another-very-long-name, another-very-long-name, another-very-long-name, another-very-long-name. 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-4402e9c4d358bdf7d8c0eba28c311f34"],"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-4402e9c4d358bdf7d8c0eba28c311f34","url":"https://github.com/advisories/GHSA-9w99-w8fq-2x8w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-9w99-w8fq-2x8w","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:53.250Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4402e9c4d358bdf7d8c0eba28c311f34"],"technology":"another-very-long-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (eea9e3cf3d973c07d09048435d4ddc496574ce222d650c228b1400d866ea3ccf)\nanother-very-long-name@1.0.1 ships a beacon.cjs that is invoked both from the declared postinstall lifecycle script and from the module's require()-time entry (index.js). On execution it collects host identifiers — hostname, install path, process.cwd(), process.version, OS metadata, and the package name — and POSTs them as JSON to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The package exposes no genuine functionality: index.js returns a Proxy whose get handler returns a no-op for every property so that bundlers consuming the package do not fail, and an author comment states that a build that completes and calls back is cleaner evidence. The destination is a bare-IP HTTP endpoint with no first-party relationship to any declared publisher, and the stub-plus-beacon shape is consistent with a dependency-confusion reconnaissance probe rather than a compatibility shim.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/malicious/npm/another-very-long-","public_affected_ranges":["= 2.0.0"]},{"certainty":"source_listed","source_ids":["sr-4402e9c4d358bdf7d8c0eba28c311f34"],"technology":"another-very-long-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (eea9e3cf3d973c07d09048435d4ddc496574ce222d650c228b1400d866ea3ccf)\nanother-very-long-name@1.0.1 ships a beacon.cjs that is invoked both from the declared postinstall lifecycle script and from the module's require()-time entry (index.js). On execution it collects host identifiers — hostname, install path, process.cwd(), process.version, OS metadata, and the package name — and POSTs them as JSON to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The package exposes no genuine functionality: index.js returns a Proxy whose get handler returns a no-op for every property so that bundlers consuming the package do not fail, and an author comment states that a build that completes and calls back is cleaner evidence. The destination is a bare-IP HTTP endpoint with no first-party relationship to any declared publisher, and the stub-plus-beacon shape is consistent with a dependency-confusion reconnaissance probe rather than a compatibility shim.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/malicious/npm/another-very-long-","public_affected_ranges":["= 1.0.1"]},{"certainty":"source_listed","source_ids":["sr-4402e9c4d358bdf7d8c0eba28c311f34"],"technology":"another-very-long-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (eea9e3cf3d973c07d09048435d4ddc496574ce222d650c228b1400d866ea3ccf)\nanother-very-long-name@1.0.1 ships a beacon.cjs that is invoked both from the declared postinstall lifecycle script and from the module's require()-time entry (index.js). On execution it collects host identifiers — hostname, install path, process.cwd(), process.version, OS metadata, and the package name — and POSTs them as JSON to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The package exposes no genuine functionality: index.js returns a Proxy whose get handler returns a no-op for every property so that bundlers consuming the package do not fail, and an author comment states that a build that completes and calls back is cleaner evidence. The destination is a bare-IP HTTP endpoint with no first-party relationship to any declared publisher, and the stub-plus-beacon shape is consistent with a dependency-confusion reconnaissance probe rather than a compatibility shim.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/malicious/npm/another-very-long-","public_affected_ranges":["= 2.0.1"]},{"certainty":"source_listed","source_ids":["sr-4402e9c4d358bdf7d8c0eba28c311f34"],"technology":"another-very-long-name","known_exclusions":[],"conditions_summary":"## Source: amazon-inspector (eea9e3cf3d973c07d09048435d4ddc496574ce222d650c228b1400d866ea3ccf)\nanother-very-long-name@1.0.1 ships a beacon.cjs that is invoked both from the declared postinstall lifecycle script and from the module's require()-time entry (index.js). On execution it collects host identifiers — hostname, install path, process.cwd(), process.version, OS metadata, and the package name — and POSTs them as JSON to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The package exposes no genuine functionality: index.js returns a Proxy whose get handler returns a no-op for every property so that bundlers consuming the package do not fail, and an author comment states that a build that completes and calls back is cleaner evidence. The destination is a bare-IP HTTP endpoint with no first-party relationship to any declared publisher, and the stub-plus-beacon shape is consistent with a dependency-confusion reconnaissance probe rather than a compatibility shim.\n\n---\n\nCredit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/ff41f6680a0ebbef2268cdb5daf253d4b400cb05/osv/malicious/npm/another-very-long-","public_affected_ranges":["= 1.1.0"]}],"null_published_at":"2026-10-31T22:13:39.931Z","source_updated_at":"2026-10-11T15:31:20.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"}