MAL-2026-10717 Malicious code in @onescience/onecode (npm)
Malicious package
Published
MAL-2026-10717 is a malicious package: @onescience/onecode (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-10717/ (Markdown: https://insights.sbomify.com/MAL-2026-10717/index.md)
- Package
- @onescience/onecode
- Registry
- npm
What is MAL-2026-10717?
MAL-2026-10717 is a malicious package in @onescience/onecode, published on 16 Jul 2026.
Official description
The npm postinstall hook runs ensurePlatformBinary(), which downloads a.tgz archive from the hardcoded bare-IP URL https://218.90.133.98:4443/onecode_tgz/onecode-<ver>/onecode-linux-x64-<ver>.tgz, extracts it via
tar -xzf, chmods the extracted file to 0o755, hardlinks it into bin/.onecode, and the shipped CLI launcher invokes it. The HTTPS request explicitly sets rejectUnauthorized: false, disabling TLS certificate verification, and no hash or signature check is performed on the downloaded artifact. The download destination is a bare IPv4 address on a non-standard port, not a publisher-owned domain or a recognized release host. The package name and launcher (@onescience/onecode) mirror the unrelated 'opencode' project — env-var fallbacks reference OPENCODE_BIN_PATH and bundled asset directories are named.opencode/session-seed and.opencode/oneskills — while the executable payload is retrieved from an unrelated hardcoded IP endpoint. Anyone controlling that host, or any on-path network attacker (TLS is disabled), can deliver arbitrary code that executes on every installer's machine.What should I do about MAL-2026-10717?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.