Which versions of dise-pkt are malicious?

The following npm versions of dise-pkt are flagged malicious: 0.0.1-security, 1.0.2. Treat any of these as compromised.

How do I remediate dise-pkt if I installed it?

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

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

Yes — dise-pkt is associated with the GHSA-jgcj-pm32-hmcj, RLMA-2026-01244 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 dise-pkt 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 dise-pkt (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dise-pkt across your stack and pipelines.

Malicious package

dise-pktnpm

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

MAL-2026-644

Immediate action

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

npm uninstall dise-pkt

What this malware does

The package dise-pkt 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.

Malicious versions

2 flagged

0.0.1-security1.0.2

Indicators of compromise (SHA-256)

58b8c2811e173e83d76597b5cb08d80de79cbc72396b7ba7957ed6c15a6003a2

b02da19d128c79fa9465ba506ff8f53abb3ef541a1da253174255be017c9fd97

506dc7788ddc372af7f55e2d03ee14c0efbdd707c32e8960a1fa7b5ab2d7eab9

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

Campaign

GHSA-jgcj-pm32-hmcjRLMA-2026-01244

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dise-pkt-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