Which versions of @syncraft-labs/core are malicious?

The following npm versions of @syncraft-labs/core are flagged malicious: 0.4.1. Treat any of these as compromised.

How do I remediate @syncraft-labs/core if I installed it?

Remove @syncraft-labs/core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @syncraft-labs/core — how do I know if it already compromised me?

If @syncraft-labs/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @syncraft-labs/core part of a known attack campaign?

Yes — @syncraft-labs/core is associated with the IN-MAL-2026-018570, GHSA-vhcg-r2h4-gx3m 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 @syncraft-labs/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @syncraft-labs/core (version 0.4.1).

Malicious package

@syncraft-labs/corenpm

Advisory published Aug 23, 2026Updated Aug 26, 2026

@syncraft-labs/core is a confirmed malicious npm package (MAL-2026-14367) that executes malicious code on install (malicious version 0.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @syncraft-labs/core (npm)

MAL-2026-14367

Immediate action

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

npm uninstall @syncraft-labs/core

What this malware does

The ESM build shipped at dist/index.js contains a heavily obfuscated payload (hex-identifier string-array + rotator produced by an obfuscator.io-style tool) injected into the body of isDevMode(), which executes on every import/require of the package. The injected loader captures Node internals onto globalThis (globalThis.r = require, globalThis.m = module, globalThis.i = "A12-synd"), then uses http/https to query Ethereum JSON-RPC endpoints (eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blockscout.com) and an Etherscan-style txlist API for a hardcoded attacker address (0xa322E5f3...), decodes and zlib-decompresses payload bytes from transaction data, and executes them via child_process.spawn. The CJS build of the same source is clean, indicating a targeted injection into the ESM entry rather than a bundler artifact. Any process importing this package fetches attacker-controlled code from a mutable on-chain dead-drop and runs it, giving the publisher arbitrary remote code execution on the installer's host with full Node capability handed to the second stage via the globalThis handoff.

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.4.1

Indicators of compromise (SHA-256)

0efe219063a966d0d2025d6c3274cbc7e9f3c0b3a1e9cdf81c7adf6dbae4d4ac

3ef1bc02a0593d257249d740d38a6ccdbd0464272090c4c94dba7eb31113bbda

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @syncraft-labs/core (version 0.4.1).
If you installed it — respond
Remove @syncraft-labs/core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @syncraft-labs/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @syncraft-labs/core on npm has been identified as a malicious package (version 0.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018570GHSA-vhcg-r2h4-gx3m

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @syncraft-labs/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database