registry / Remote code execution / boxy-semver
boxy-semver
Boxy semver provider for microservice architecture
This report shows the evidence for boxy-semver@35.3.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 unrelated to the declared semver API. Absence of an npm lifecycle hook does not mitigate the runtime RCE path.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Arbitrary remote code execution as the consuming application's user.
Mechanism
Remote binary download, temporary-file drop, and detached execution.
Attack narrative
The package’s public entrypoint silently requires _init.js. On import, it attempts to retrieve a payload from hard-coded worker hosts, with DNS-TXT retrieval as fallback, stores it in a temp directory, marks it executable on Unix, and launches it detached through a shell or cmd.exe. A marker only throttles repeated execution.
AI rationale
This is concrete import-time remote payload execution unrelated to the declared semver API. Absence of an npm lifecycle hook does not mitigate the runtime RCE path.
Evidence
package.jsonindex.js_init.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf99-9b3.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.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 binaries over HTTPS or DNS TXT.
- _init.js writes, chmods, and detached-spawns downloaded payloads.
- Remote hosts include oob-worker.cf99-9b3.workers.dev and dl.wel1.ru subdomains.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by package entrypoints.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_init.jsView file
5const path = require("path");
L6: const https = require("https");
L7: const os = require("os");
...
L47: const MAX_AGE = 23264;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: if (e || !rr || !rr.length) return r("");
Critical
5Trigger-reachable chain: manifest.main -> index.js -> _init.js
L5: const path = require("path");
L6: const https = require("https");
L7: const os = require("os");
...
L47: const MAX_AGE = 23264;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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 · L5119try {
L120: const cp = require("child_process");
L121: if (isWin) {
Findings
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-semver@35.3.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-semver@35.3.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.