Which versions of @tonsdk/core are malicious?

The following npm versions of @tonsdk/core are flagged malicious: 0.9.3. Treat any of these as compromised.

How do I remediate @tonsdk/core if I installed it?

@tonsdk/core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @tonsdk/core — how do I know if it already compromised me?

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

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

Malicious package

@tonsdk/corenpm

@tonsdk/core is a confirmed malicious npm package (MAL-2026-5564) that opens a backdoor for remote access (malicious version 0.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @tonsdk/core (npm)

MAL-2026-5564

Immediate action

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

npm uninstall @tonsdk/core

What this malware does

@tonsdk/core impersonates the legitimate @ton/core TON blockchain SDK. On npm install, scripts/postinstall.js executes automatically and performs two attacker-controlled actions against a hardcoded bare-IP C2 at 213.218.160.189 (ports 8080 and 80) over plaintext HTTP. First, it base64-encodes a JSON fingerprint of the installer host — hostname, username, platform, arch — and sends it as a GET query string to /s?q=<base64>, leaking host identifiers on every install. Second, it fetches a response payload, optionally XOR-decrypts it, and passes the result to eval(), giving the operator arbitrary remote code execution in the installer's Node process. The script also probes for VM/sandbox/analyst tooling (vmtoolsd, vboxservice, wireshark, x64dbg, ida) to suppress execution in researcher environments. The package description and name target developers searching for TON SDK tooling; the repository URL (aspect-build/tonsdk) is unrelated to the real TON foundation.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

0.9.3

Indicators of compromise (SHA-256)

d9a9a70e3d8b322df960cb96b195f74693eb4d2ea284680e4cfb41a33f1848f8

57c76201082cb24093c4db6ec9c7c86cd0088eb36159e05bb61bb38be791188e

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tonsdk/core (version 0.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tonsdk/core across your stack and pipelines.
If you installed it — respond
@tonsdk/core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @tonsdk/core 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 @tonsdk/core 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. @tonsdk/core on npm has been identified as a malicious package (version 0.9.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005530GHSA-hw5x-gw43-m4mx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tonsdk/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database