Which versions of dstny-utils are malicious?

The following npm versions of dstny-utils are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate dstny-utils if I installed it?

Remove dstny-utils 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 dstny-utils — how do I know if it already compromised me?

If dstny-utils 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.

How do I find dstny-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dstny-utils (version 999.0.0).

Malicious package

dstny-utilsnpm

Advisory published Jan 3, 2026Updated Jan 8, 2026

dstny-utils is a confirmed malicious npm package (MAL-2026-30) that executes malicious code on install (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dstny-utils (npm)

MAL-2026-30

Immediate action

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

npm uninstall dstny-utils

What this malware does

The package dstny-utils was found to contain malicious code.

The OpenSSF Package Analysis project identified 'dstny-utils' @ 999.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

4674a7ac69b281fcdc9a176b0fa79bd2efe656078a5d7038cb725a4c58f0d294

b284da9586db3d25955c197277419786676841a572ee83eb99a463072eff3dec

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dstny-utils (version 999.0.0).
If you installed it — respond
Remove dstny-utils 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 dstny-utils 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. dstny-utils on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks dstny-utils-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

Explore

All malware advisories How O3 detects malware Vulnerability database