dotenv-syncPyPI
Malicious code in dotenv-sync (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
On Windows, src/envsync/__init__.py (lines 39-44) unconditionally calls ctypes.CDLL on a bundled ~2.9MB PE file _parser.pyd at top-level import, wrapped in try:... except: pass. Loading a PE via ctypes.CDLL invokes LoadLibraryA, which executes the DLL's DllMain entry point — arbitrary native code runs on every import dotenv_sync / import envsync with the installer's user privileges, silently. No symbol from the.pyd is ever called from Python; the sole effect of the CDLL call is to execute the binary. The package's README advertises 'zero dependencies', 'Pure Python parser', and 'nothing to audit', and a ~60-line pure-Python parser already exists in parse.py — so the native load is undisclosed and unnecessary for the advertised functionality. pyproject.toml line 78 force-includes two byte-identical copies of the PE (_parser.pyd and __parser.pyd, sha256 b1aace6c70312a39ca39e6bba1d9abc6aaf9b23171089b1a548adc89f67f83c3) into both the wheel and sdist; the binaries' strings show only register-save prologues with no readable text, imports, or URLs — consistent with a packed payload. There is no Extension(), no setuptools/maturin/cmake build configuration, and no source for the binary. The dotenv-sync name and dotenv-sync/envsync CLI entries impersonate the python-dotenv / dotenv-linter / npm envsync ecosystem; author is generic ('envsync contributors') and all project URLs point only at the package's own PyPI page, with no inspectable upstream.
During import, package loads embedded native extension module. This library hooks on loading, spawns a new system process and likely attempts to inject the encrypted payload in it for further execution (T1055.012). The code uses heavy analysis evasion techniques. Decrypted payload revealed capabilities to steal all kind of credentials (browsers data, AI tools, env variables, SSH keys, ...), inject code to redirect cryptocurrency transactions, spy-like activities (screenshots, keylogger) and worm-like activities using discovered GitHub tokens to publish malicious code into CI. It establishes persistence in %LOCALAPPDATA%\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe and also attempts to perform lateral movement in Kubernetes and AWS environments.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-06-syncagents
Reasons (based on the campaign):
-
native-extension
-
infostealer
-
worm
-
exfiltration-crypto
-
exfiltration-credentials
-
uses-telegram-bot
-
keylogger
-
clipboard-stealing
-
exfiltration-ssh-keys
-
The package contains code to detect if it is running in a sandbox environment.
-
obfuscation
-
exfiltration-browser-data
-
exfiltration-env-variables
-
persistence
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dotenv-sync (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dotenv-sync across your stack and pipelines.
If you installed it — respond
dotenv-sync is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dotenv-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 dotenv-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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks dotenv-sync-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.