Which versions of deepl-sync are malicious?

The following npm versions of deepl-sync are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate deepl-sync if I installed it?

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.

I already installed deepl-sync — how do I know if it already compromised me?

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

Yes — deepl-sync is associated with the GHSA-qvrg-265v-cqvc 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 deepl-sync 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 deepl-sync (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deepl-sync across your stack and pipelines.

Malicious package

deepl-syncnpm

Malicious code in deepl-sync (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for deepl-sync (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging deepl-sync across your stack and pipelines.
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.
Did it already run?
If deepl-sync 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 deepl-sync 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. 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

github.com

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.

Malware detection Runtime egress monitoring