Which versions of boxy-adapter-tramvai are malicious?

The following npm versions of boxy-adapter-tramvai are flagged malicious: 35.6.6. Treat any of these as compromised.

How do I remediate boxy-adapter-tramvai if I installed it?

boxy-adapter-tramvai is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed boxy-adapter-tramvai — how do I know if it already compromised me?

If boxy-adapter-tramvai was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is boxy-adapter-tramvai part of a known attack campaign?

Yes — boxy-adapter-tramvai is associated with the IN-MAL-2026-015351 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find boxy-adapter-tramvai across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-adapter-tramvai (version 35.6.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-adapter-tramvai across your stack and pipelines.

Malicious package

boxy-adapter-tramvainpm

boxy-adapter-tramvai is a confirmed malicious npm package (MAL-2026-13028) that steals credentials and exfiltrates sensitive data (malicious version 35.6.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in boxy-adapter-tramvai (npm)

MAL-2026-13028

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall boxy-adapter-tramvai

What this malware does

On library load, index.js requires./runtime.js, which selects a platform-specific staging path, fetches an opaque binary from obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64 fallback under *.dl.wel1.ru (sdk/ext/pkg/net subdomains), writes the bytes to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmods 0755, and detached-spawns via /bin/sh -c or cmd. Hostnames are reconstructed at runtime via Array.join fragments to evade static analysis; a cache marker file at /tmp/.analytics_state gates re-execution, and env vars named DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK are used as a telemetry cover story. The DNS-TXT channel reads a chunk count from c.<domain> then reassembles base64 fragments from 0.<domain>..N.<domain> into an executable buffer, providing a firewall-evading secondary delivery path. Payload bytes are unpinned, unverified, and staged under filenames impersonating OS diagnostic tools. The name mimics the legitimate @tramvai ecosystem.

Malicious versions

1 flagged

35.6.6

Indicators of compromise (SHA-256)

d20d5167abc8703b7b09a0d9698e6d0fd060f4378dfa11ab469af3e6805cfc8e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-adapter-tramvai (version 35.6.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-adapter-tramvai across your stack and pipelines.
If you installed it — respond
boxy-adapter-tramvai is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If boxy-adapter-tramvai was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks boxy-adapter-tramvai before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. boxy-adapter-tramvai on npm has been identified as a malicious package (version 35.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015351

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks boxy-adapter-tramvai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database