Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/271 feeds/APIs · 464/464 docs · 8/9 advisories · checked 04:30 UTC Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in ap3-foundations-ui (npm)

Exact source revision recorded 26 Oct 2026 02:35:24 UTC. It does not establish the source's current position. Latest evidence.

osv · MAL-2026-17806

Published

ap3-foundations-ui describes itself as a security research PoC for dependency confusion and does not identify an upstream package it copies. Its `preinstall` hook runs `node index.js` during `npm install`; the script sends the package name and version, hostname, username, home directory, working directory, platform, architecture, and CI flag to `https://webhook.site/7dbd5e4e-3156-427f-b383-30c14d845587`. The npm account vikkuthetester22 published it on 2026-10-12. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7469eefaab624821647b4e412c4ceac1f422d4857b8484767041fdc355398477) The package's preinstall hook runs index.js, which collects installer host identifiers (os.hostname(), os.userInfo().username, os.homedir(), process.cwd(), os.platform(), os.arch(), and process.env.CI) and POSTs them as JSON to a hardcoded third-party collector at https://webhook.site/7dbd5e4e-3156-427f-b383-30c14d845587. The behavior fires automatically on `npm install` without caller consent. The package is published at version 99.0.1 under a name consistent with an internal/private namespace, matching the shape of a dependency-confusion beacon used to confirm successful name hijack in a target environment. The exfiltrated fields identify the installing host, user account, working directory, and CI status — information useful for targeting follow-on attacks against the organization whose build pulled the package. ## Source: ghsa-malware (2a08a293df7b3bdb17da1149e35d01f30c8b4e27a90bae6dd0b5c93e2e67c606) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Source published
12 Oct 2026 00:57:37 UTC
Source modified
26 Oct 2026 01:45:24 UTC
Observed here
26 Oct 2026 02:35:24 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 04:30 UTC · 271 of 271 readable · 269 fully read · documentation 464/464 current