Malicious code in claims-ac1 (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

claims-ac1 1.0.0 contains only a package.json declaring a single dependency, node-ac2, that is not fetched from the npm registry but from a tarball in the GitHub repository `GamerD11/ping_test` (`https://github.com/GamerD11/ping_test/raw/main/node-ac2.tgz`). That tarball has no code and in turn depends on node-ac3, another tarball in the same repository (`https://github.com/GamerD11/ping_test/raw/main/node-ac3.tgz`), whose `preinstall` script runs `node index.js` and silently ignores errors. The script reads a collector host name from `https://raw.githubusercontent.com/GamerD11/ping_test/main/test.txt` (an oastify.com host when observed) and does nothing if the file is empty; otherwise it sends an HTTPS POST to that host on port 443, path `/health`, with certificate verification disabled, containing the Node.js version, home directory, working directory, platform and architecture. The package has no legitimate functionality, the data is collected without the user's knowledge, and…

Published by the source

31 Oct 2026, 18:22 UTC

Last modified by the source

2 Nov 2026, 14:30 UTC

Source last checked

3 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 3 Nov 2026

   Amended from osv record MAL-2026-18450

2. Revision 1 · created · 2 Nov 2026

   Published from osv record MAL-2026-18450

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-p5qq-93vh-5c8h

Advisory: Malicious code in claims-ac1 (npm)
IDs: GHSA-p5qq-93vh-5c8h
Record: https://patchnext.com/advisories/mal-2026-18450 (revision 2, source checked 3 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm claims-ac1: affected every version

## Suggested inspection (read-only)
- `npm ls claims-ac1 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on claims-ac1.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18450 (OSV record MAL-2026-18450 lists affected ranges: npm claims-ac1 >=1.0.0 <=1.0.0)
- Verified: https://osv.dev/vulnerability/MAL-2026-18450 (OSV record MAL-2026-18450 lists affected ranges: npm claims-ac1 >=0)

Commands are suggestions: review each one before running it.