registry / Remote code execution / certificates-revocation-utils
certificates-revocation-utils
shared utilities
This report shows the evidence for certificates-revocation-utils@35.1.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-aiThis is a concrete import-time remote-code-execution chain, not merely a network or telemetry primitive. The payload source is remote and unverified, then executed without user action.
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 arbitrary code execution under the importing process account.
Mechanism
import-time remote payload download and detached native execution
Attack narrative
The main entrypoint imports `_vendor.js` during normal package loading. That module selects a platform payload path, downloads bytes from obfuscated hosts or reconstructs them from DNS TXT records, drops the result into a temporary directory, marks it executable on Unix, and starts it via a detached shell or cmd.exe process. The behavior is hidden behind telemetry-style naming and has no relation to the documented utility API.
AI rationale
This is a concrete import-time remote-code-execution chain, not merely a network or telemetry primitive. The payload source is remote and unverified, then executed without user action.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp
Network endpoints8
oob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devsdk.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:30 imports _vendor on every package import.
- _vendor.js:24-46 assembles four workers.dev hosts and .ru DNS domains.
- _vendor.js:149-160 downloads a platform payload or reconstructs one from DNS TXT.
- _vendor.js:169-175 writes the payload to temp, chmods it, and executes it detached.
- _vendor.js:178 invokes this chain at module load.
Evidence against
- package.json has no lifecycle scripts.
- Public utilities in index.js are otherwise simple local helpers.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_vendor.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L48: const STAMP_TTL = 19912;
L49: const _l = (...a) => process.stderr.write("");
L50:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L4: const os = require("os");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L48: const STAMP_TTL = 19912;
L49: const _l = (...a) => process.stderr.write("");
L50:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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.
_vendor.jsView on unpkg · L4Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to certificates-revocation-utils@35.1.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing certificates-revocation-utils@35.1.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.