Which versions of devkitx are malicious?

The following npm versions of devkitx are flagged malicious: 5.6.4. Treat any of these as compromised.

How do I remediate devkitx if I installed it?

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

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

Yes — devkitx is associated with the GHSA-x77g-g3p5-frhh 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 devkitx 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 devkitx (version 5.6.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devkitx across your stack and pipelines.

Malicious package

devkitxnpm

Malicious code in devkitx (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2871

Immediate action

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

npm uninstall devkitx

What this malware does

The package devkitx 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.

The OpenSSF Package Analysis project identified 'devkitx' @ 5.6.4 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

5.6.4

Indicators of compromise (SHA-256)

092c5395fc632b822424847ce7aa8676a345a6ca0ef7b996fe508ea6cb445f07

533ba14fdd7bd4a9722b6958993e6814b7f5b492ed9664250012deab8161401b

6344b4de933cb52dfd12ac4a38d68b3ea57498248f6cb291252a1a56d9963b55

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

Campaign

GHSA-x77g-g3p5-frhh

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks devkitx-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