Which versions of @workoscalif/sudoku are malicious?

The following npm versions of @workoscalif/sudoku are flagged malicious: 1.4.0. Treat any of these as compromised.

How do I remediate @workoscalif/sudoku if I installed it?

@workoscalif/sudoku 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 @workoscalif/sudoku — how do I know if it already compromised me?

If @workoscalif/sudoku 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 @workoscalif/sudoku part of a known attack campaign?

Yes — @workoscalif/sudoku is associated with the IN-MAL-2026-015841 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 @workoscalif/sudoku 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 @workoscalif/sudoku (version 1.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @workoscalif/sudoku across your stack and pipelines.

Malicious package

@workoscalif/sudokunpm

@workoscalif/sudoku is a confirmed malicious npm package (MAL-2026-13366) that steals credentials and exfiltrates sensitive data (malicious version 1.4.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @workoscalif/sudoku (npm)

MAL-2026-13366

Immediate action

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

npm uninstall @workoscalif/sudoku

What this malware does

@workoscalif/[email protected] declares postinstall: node scripts/postinstall.mjs, which spawns vendor/gridgen-${process.platform}-${process.arch} on npm install. The linux-x64 and darwin-x64 slots both contain the same 33,648,788-byte ELF Go binary (sha256 05b69666193e8fa719c37df22833bf36a120b15e2408a9ecd47e34f140a44420), including a Mach-O slot that actually contains an ELF. The shipped C source native/gridgen.c is ~250 lines of pure computation with no I/O, and the arm64 binaries compile to 34-67 KB from that source; the x64 binaries are ~500x larger, are Go rather than compiled C, and contain an HTTP client in their string table. The README describes a tiny sockets/env-free sudoku puzzle generator (34,520 B linux ELF, 13,160 B darwin Mach-O), which contradicts what actually ships. Suspicious domain-shaped tokens uaguBrDY.tk, id7TJrH.ga, and gIcKT3hfVC.co appear in the Go binary's strings. The wrapper, README, and matching-arch binaries form a cover story that conceals an unrelated binary payload dropped and executed on x64 hosts at install time.

Malicious versions

1 flagged

1.4.0

Indicators of compromise (SHA-256)

09e5ade8ff253759644f519075c5e54fe1b927aa73d64624efaddc83af9098ba

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 @workoscalif/sudoku (version 1.4.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @workoscalif/sudoku across your stack and pipelines.
If you installed it — respond
@workoscalif/sudoku 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 @workoscalif/sudoku 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 @workoscalif/sudoku 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. @workoscalif/sudoku on npm has been identified as a malicious package (version 1.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015841

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @workoscalif/sudoku-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