registry / Remote code execution / claims-get-error-string
claims-get-error-string
Claims get error string provider for microservice architecture
This report shows the evidence for claims-get-error-string@35.5.9, 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-aiThe malicious loader is import-reachable and performs unverified remote payload execution without user consent. Lack of npm lifecycle hooks does not mitigate runtime compromise.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package entrypoint.
Impact
Unconsented remote code execution as the importing application's user.
Mechanism
Remote binary download, temporary drop, chmod, and detached execution.
Attack narrative
Requiring index.js silently loads _ext.js. Its bootstrap routine rate-limits with a temp stamp, fetches a platform-specific binary from hard-coded worker hosts or DNS TXT records, writes it under /var/tmp (or Windows Temp), marks it executable on Unix, and spawns it detached through /bin/sh or cmd.exe. The bundled telemetry module contains the same downloader-and-launcher pattern.
AI rationale
The malicious loader is import-reachable and performs unverified remote payload execution without user consent. Lack of npm lifecycle hooks does not mitigate runtime compromise.
Evidence
package.jsonindex.js_ext.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.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 _ext.js on every package require.
- _ext.js downloads platform payloads from three worker hosts.
- _ext.js falls back to DNS TXT payloads under *.wel1.ru.
- Downloaded bytes are written to temp, chmodded, and detached-spawned.
- No checksum, signature, or user action gates execution.
Evidence against
- package.json has no lifecycle scripts.
- No credential-harvesting logic was identified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_ext.jsView file
2L3: const https = require("https");
L4: const os = require("os");
...
L46: const STAMP_TTL = 21137;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: 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
2Trigger-reachable chain: manifest.main -> index.js -> _ext.js
L2:
L3: const https = require("https");
L4: const os = require("os");
...
L46: const STAMP_TTL = 21137;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: 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.
_ext.jsView on unpkg · L2120try {
L121: const cp = require("child_process");
L122: if (isWin) {
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_ext.js
CriticalTrigger Reachable Dangerous Capability_ext.js
HighChild Process_ext.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to claims-get-error-string@35.5.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing claims-get-error-string@35.5.9. 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.