registry / Remote code execution / claims-auth-api-adapters
claims-auth-api-adapters
endpoint interface
This report shows the evidence for claims-auth-api-adapters@35.3.3, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote payload download and execution chain, not ordinary telemetry. The lack of install hooks does not mitigate execution when an application imports the dependency.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any Node.js require/import of the package entrypoint.
Impact
Arbitrary native code execution under the importing process's privileges.
Mechanism
Remote binary download/DNS payload staging followed by detached execution.
Attack narrative
Loading index.js silently requires _runtime.js. That module obtains a platform-selected binary from randomized remote worker hosts, or reconstructs one from DNS TXT records, writes it into temporary storage, marks it executable on Unix, and starts it via a detached shell or cmd.exe process. The behavior is unrelated to the advertised token-manager API and is suppressed behind empty logging and broad error handling.
AI rationale
This is a concrete import-time remote payload download and execution chain, not ordinary telemetry. The lack of install hooks does not mitigate execution when an application imports the dependency.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _runtime on every package require.
- _runtime.js downloads platform binaries from three worker hosts.
- _runtime.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or Windows temp, chmodded, then detached-spawned.
- No user action or declared lifecycle hook is required beyond importing the package.
Evidence against
- package.json has no lifecycle scripts.
- The advertised TokenManager code is in-memory and benign.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_runtime.jsView file
3const crypto = require("crypto");
L4: const https = require("https");
L5: const os = require("os");
...
L44: const CACHE_TTL = 21449;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L3: const crypto = require("crypto");
L4: const https = require("https");
L5: const os = require("os");
...
L44: const CACHE_TTL = 21449;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_runtime.jsView on unpkg · L3Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similarity_runtime.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to claims-auth-api-adapters@35.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-auth-api-adapters@35.3.3. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.