Which versions of salesforce-sysutils-diagnostics are malicious?

The following PyPI versions of salesforce-sysutils-diagnostics are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate salesforce-sysutils-diagnostics if I installed it?

salesforce-sysutils-diagnostics 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 salesforce-sysutils-diagnostics — how do I know if it already compromised me?

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

Yes — salesforce-sysutils-diagnostics is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-006660, IN-MAL-2026-006661 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 salesforce-sysutils-diagnostics 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 salesforce-sysutils-diagnostics (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging salesforce-sysutils-diagnostics across your stack and pipelines.

Malicious package

salesforce-sysutils-diagnosticsPyPI

Malicious code in salesforce-sysutils-diagnostics (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5754

Immediate action

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

pip uninstall salesforce-sysutils-diagnostics

What this malware does

setup.py unconditionally invokes curl at install time to POST the contents of /tmp/fake-keys.json to https://webhook.site/20ed745d-ee73-4b79-ab06-5b106255c38c, an anonymous request-capture endpoint. stderr is redirected to DEVNULL to suppress install-time output. The package additionally impersonates the Salesforce brand (name 'salesforce-sysutils-diagnostics') with no Author or Home-page metadata in PKG-INFO, consistent with a brand-confusion lure. Any developer or build system that runs pip install salesforce-sysutils-diagnostics will trigger an outbound POST to the attacker-controlled webhook on every install.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

df69f7ee7e4cb191b719367d5d707c8c244f50c35d1af182e5b9cec73dd1937c

59e4ce1338f2439a1a5b2d257b96aadaef4a9c2883f6787343856728514bd148

f7c37a22e941d37810aecad4c26a58e003977e4ca1715d733c99b1d7863debcf

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 salesforce-sysutils-diagnostics (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging salesforce-sysutils-diagnostics across your stack and pipelines.
If you installed it — respond
salesforce-sysutils-diagnostics 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 salesforce-sysutils-diagnostics 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 salesforce-sysutils-diagnostics 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. salesforce-sysutils-diagnostics on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-006660IN-MAL-2026-006661

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks salesforce-sysutils-diagnostics-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