Which versions of syncgrove are malicious?

The following npm versions of syncgrove are flagged malicious: 1.4.0. Treat any of these as compromised.

How do I remediate syncgrove if I installed it?

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

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

Yes — syncgrove is associated with the IN-MAL-2026-010675 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 syncgrove 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 syncgrove (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 syncgrove across your stack and pipelines.

Malicious package

syncgrovenpm

Malicious code in syncgrove (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10680

Immediate action

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

npm uninstall syncgrove

What this malware does

The package's postinstall lifecycle script contacts a hardcoded plain-HTTP endpoint at http://player.sweeprovider.org, retrieves a key via /getKey.php and an AES-CBC encrypted payload via /generateRandomKey.php, decrypts the payload using CryptoJS with a hardcoded key suffix, and passes the resulting string to child_process.exec. This causes attacker-supplied, mutable, obfuscated shell content to run automatically on the installer's machine during npm install. The package's README presents it as a trivial 'greet' module, which does not match the actual install-time behavior. The remote host is unauthenticated and served over plain HTTP, so the fetched command body is both attacker-mutable and MITM-modifiable.

Malicious versions

1 flagged

1.4.0

Indicators of compromise (SHA-256)

6c96b3528ab792944d243b00ae61facc33740850b5cb2ed19671fd6732e43494

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for syncgrove (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 syncgrove across your stack and pipelines.
If you installed it — respond
Remove syncgrove 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 syncgrove 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 syncgrove 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. syncgrove 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-010675

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks syncgrove-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