Which versions of turing-sdk are malicious?

The following npm versions of turing-sdk are flagged malicious: 1.1.3. Treat any of these as compromised.

How do I remediate turing-sdk if I installed it?

turing-sdk 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 turing-sdk — how do I know if it already compromised me?

If turing-sdk 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 turing-sdk part of a known attack campaign?

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

Malicious package

turing-sdknpm

Malicious code in turing-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4696

Immediate action

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

npm uninstall turing-sdk

What this malware does

package.json declares turing-code as an HTTPS tarball dependency at https://turing.tap365.org/v1.1.2/turing-code-1.1.2.tgz, bypassing the npm registry entirely. Any npm install turing-sdk resolves and installs that tarball, whose contents are mutable on the author's host and never seen by registry scanners. Per the package's own README, that dependency downloads a turing binary at install. The published index.js main entry is obfuscator.io-style obfuscated (rotated string-array decoder, hex-named identifiers, self-defending IIFE) and acts as a thin wrapper that spawns the sibling turing binary, passing the caller's API keys through env vars (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, etc.). Default provider presets route requests to *.tap365.org gateway hosts (e.g. grok74.tap365.org). The combination — off-registry mutable tarball source + opaque downloaded binary + obfuscated wrapper that hands user credentials to that binary + author-operated gateway as default routing target — gives the publisher a free channel to ship arbitrary bytes to installers and to receive caller-supplied API keys.

Malicious versions

1 flagged

1.1.3

Indicators of compromise (SHA-256)

01af0d34d23b6ed4e61390a21baec8c1bb81080c04945293a7e4ba8d20277ca6

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

Campaign

IN-MAL-2026-003759

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks turing-sdk-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