Which versions of sync365 are malicious?

The following npm versions of sync365 are flagged malicious: 2.14.51. Treat any of these as compromised.

How do I remediate sync365 if I installed it?

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

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

Yes — sync365 is associated with the GHSA-47cx-6mp8-rw9q, RLMA-2025-04045, RLUA-2026-01603 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 sync365 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sync365 (version 2.14.51).

Malicious package

sync365npm

Advisory published Jul 8, 2025Updated Mar 19, 2026

sync365 is a confirmed malicious npm package (MAL-2025-5731) that executes malicious code on install (malicious version 2.14.51). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sync365 (npm)

MAL-2025-5731

Immediate action

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

npm uninstall sync365

What this malware does

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

2.14.51

Indicators of compromise (SHA-256)

2003136f074fe6e477c1a6a3458258fb4a9b375093b0520cafc082e4ff537f39

7c98eaed1f69e622ee85a7bfdb54f814c77e96b090145b8db632880998d4aa26

1094a2dbea1914dba065cf508bca48a74cc30131bcc5295032a1e09f352ebc5e

3fffa0bb67e665724f4db1fdaed9541c2ae916bdb660db6d015c6baeba8550af

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sync365 (version 2.14.51).
If you installed it — respond
Remove sync365 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 sync365 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. sync365 on npm has been identified as a malicious package (version 2.14.51 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-47cx-6mp8-rw9qRLMA-2025-04045RLUA-2026-01603

References

Credits

ReversingLabs · finder

Detect & block this

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