MAL-2026-16443 Malicious code in my-company-device (npm)
Malicious package
Published
MAL-2026-16443 is a malicious package: my-company-device (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16443/ (Markdown: https://insights.sbomify.com/MAL-2026-16443/index.md)
- Package
- my-company-device
- Registry
- npm
What is MAL-2026-16443?
MAL-2026-16443 is a malicious package in my-company-device, published on 23 Sep 2026.
Official description
Running
npx my-company-device appends a hardcoded ssh-ed25519 public key labelled sunyiting-macmini to the installer's ~/.ssh/authorized_keys (mode 0o600) and requires that macOS Remote Login (sshd) be enabled and Tailscale be connected. The tool also copies device-worker.mjs into ~/.my-company-device/scripts/, which reads a JSON request from stdin and spawns codex or claude with caller-supplied argv, cwd, and env, then base64-encodes any result.md in that cwd and emits it on stdout. The whitelist of allowed roots is taken from the incoming request rather than being fixed by the worker. Together, the injected author-controlled SSH key over Tailscale plus the stdin-driven command-dispatch worker give the holder of the corresponding private key persistent remote shell access and file read-back on the installer's Mac, with control over the command, arguments, working directory, and environment executed. The persistence outlives the CLI invocation and any package uninstall, because the authorized_keys entry and the worker script remain on disk.What should I do about MAL-2026-16443?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.