What does the dgsinstaller malware do?

Installing package downloads and install an infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2023-11-dgsinstaller Reasons (based on the campaign): - The package overrides the install command in setup.py to execute malicious code during installation. - infostealer - Downloads and executes a remote malicious script.

Which versions of dgsinstaller are malicious?

The following PyPI versions of dgsinstaller are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate dgsinstaller if I installed it?

dgsinstaller 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.

I already installed dgsinstaller — how do I know if it already compromised me?

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

Yes — dgsinstaller is associated with the 2023-11-dgsinstaller 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 dgsinstaller 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 dgsinstaller (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dgsinstaller across your stack and pipelines.

Malicious package

dgsinstallerPyPI

Malicious code in dgsinstaller (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12254

Immediate action

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

pip uninstall dgsinstaller

What this malware does

Installing package downloads and install an infostealer

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2023-11-dgsinstaller

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
infostealer
Downloads and executes a remote malicious script.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

7d9d4bd4063d551b8389acb95d2d08a923cf1ce9aad4afdfacdf2a094cd9b4c3

f90b0387462eccb87e3b6d3b542cfdcfe3083873083f00a7ac5120c64b800f98

419687796c75fb58b8c4ea485722f1dbeeccdeb532b547fd583f8a8df7a49dfe

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dgsinstaller (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dgsinstaller across your stack and pipelines.
If you installed it — respond
dgsinstaller 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 dgsinstaller 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 dgsinstaller 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. dgsinstaller on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2023-11-dgsinstaller

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks dgsinstaller-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring