registry / Remote code execution / boxy-sticky-providers
boxy-sticky-providers
Boxy sticky providers abstraction layer
This report shows the evidence for boxy-sticky-providers@35.1.5, 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 concrete import-time remote payload execution with no integrity validation or user action beyond importing the package. Absence of an npm lifecycle hook does not mitigate the reachable entrypoint behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Requiring the package entrypoint.
Impact
Arbitrary remote code executes as the importing process user.
Mechanism
import-time staged payload download and detached execution
Attack narrative
The public entrypoint suppresses errors while importing _init.js. That module immediately retrieves a platform-specific binary from concealed HTTPS hosts, with DNS-TXT payload retrieval as fallback, writes it under a misleading temporary filename, marks it executable on Unix, and starts it detached through a shell or cmd.exe. The same loader pattern also appears in the otherwise unreferenced telemetry module.
AI rationale
This is concrete import-time remote payload execution with no integrity validation or user action beyond importing the package. Absence of an npm lifecycle hook does not mitigate the reachable entrypoint behavior.
Evidence
package.jsonindex.js_init.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.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 imports _init.js on every package import.
- _init.js downloads platform payloads over HTTPS or DNS TXT.
- _init.js writes payloads to temp paths, chmods them, and launches detached shells.
- Payload hosts are obfuscated Cloudflare Workers and wel1.ru DNS domains.
Evidence against
- package.json has no lifecycle hooks.
- No credential or environment-value harvesting was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_init.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L41: const COOLDOWN = 19826;
L42: const _l = (...a) => process.stderr.write("");
L43:
...
L52: const isWin = _p("platform") === "win32";
L53: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L54: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L87: try {
L88: require("dns").resolveTxt(d, (e, rr) => {
L89: if (e || !rr || !rr.length) return r("");
Critical
3Trigger-reachable chain: manifest.main -> index.js -> _init.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L41: const COOLDOWN = 19826;
L42: const _l = (...a) => process.stderr.write("");
L43:
...
L52: const isWin = _p("platform") === "win32";
L53: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L54: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L87: try {
L88: require("dns").resolveTxt(d, (e, rr) => {
L89: 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.
_init.jsView on unpkg · L3Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_init.js
CriticalTrigger Reachable Dangerous Capability_init.js
HighChild Process_init.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to boxy-sticky-providers@35.1.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-sticky-providers@35.1.5. 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.