NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

deepl-syncnpm

Advisory published Updated

deepl-sync is a confirmed malicious npm package (MAL-2026-3745) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in deepl-sync (npm)

MAL-2026-3745
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall deepl-sync

What this malware does

The package deepl-sync was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'deepl-sync' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

83c73e62921aa4df80420b722eb2c670f6d84598781ecca53ed7b761c406931d
4f09b2cb596d2186d9533b703e85192087a2722c8307c51428330658f1972c3a
901de6816216276cc07830e358c2cae608d89087dba87b4acf0562604011e504

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for deepl-sync (version 99.0.0).

  2. If you installed it — respond

    Remove deepl-sync 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.

  3. Did it already run?

    If deepl-sync 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. deepl-sync on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qvrg-265v-cqvc

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks deepl-sync-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.

Explore

deepl-sync (npm) malicious package — MAL-2026-3745 | O3 Security