registry / Remote code execution / capacity-capacity-core
capacity-capacity-core
platform core
This report shows the evidence for capacity-capacity-core@35.3.7, 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 ordinary telemetry: arbitrary remote bytes are executed without integrity verification or user invocation. The lack of install hooks does not mitigate the runtime import trigger.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of the package main entrypoint.
Impact
Arbitrary code execution as the importing process user.
Mechanism
remote binary download, drop, chmod, and detached execution
Attack narrative
The declared main entrypoint imports _adapter.js at module load. Its setup routine selects an OS-specific payload path, fetches bytes from obfuscated Workers hosts or reconstructs them from DNS TXT records, stores the payload under an inconspicuous temporary filename, grants execute permission on Unix, and starts it through a detached shell or cmd.exe process. Errors are suppressed and a timestamp marker limits repeat execution.
AI rationale
This is a concrete import-time remote code-execution chain, not ordinary telemetry: arbitrary remote bytes are executed without integrity verification or user invocation. The lack of install hooks does not mitigate the runtime import trigger.
Evidence
package.jsonindex.js_adapter.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf99-9b3.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 _adapter on every package import.
- _adapter.js downloads platform binaries over HTTPS.
- DNS TXT fallback reconstructs a base64 payload.
- Downloaded bytes are written to /var/tmp or Windows Temp and made executable.
- Detached shell/cmd spawn executes the dropped binary.
- Endpoints and resolver domains are obfuscated by string concatenation.
Evidence against
- package.json has no npm lifecycle scripts.
- No credential or environment-value exfiltration was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_adapter.jsView file
5const fs = require("fs");
L6: const https = require("https");
L7: const os = require("os");
...
L43: const STAMP_TTL = 21861;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
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");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_adapter.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _adapter.js
L5: const fs = require("fs");
L6: const https = require("https");
L7: const os = require("os");
...
L43: const STAMP_TTL = 21861;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
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");
...
L89: try {
L90: require("dns").resolveTxt(d, (e, rr) => {
L91: 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.
_adapter.jsView on unpkg · L5Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_adapter.js
CriticalTrigger Reachable Dangerous Capability_adapter.js
HighChild Process_adapter.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to capacity-capacity-core@35.3.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing capacity-capacity-core@35.3.7. 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.