Which versions of best_gpio_controller are malicious?

The following npm versions of best_gpio_controller are flagged malicious: 1.0.10. Treat any of these as compromised.

How do I remediate best_gpio_controller if I installed it?

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

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

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

Malicious package

best_gpio_controllernpm

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

MAL-2025-191072

Immediate action

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

npm uninstall best_gpio_controller

What this malware does

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

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.10

Indicators of compromise (SHA-256)

3579a1c163ee427931fe37ffebb2a3f908e7c0b6d3625b8e9402961238949a06

15635bceffa3e60c6f3c62168a6eec8062412de0b10f6ecd63e76485e4a1196e

4b598d2978754ee5475c3bd96f57df9ebcd271bf5ecb0201c94f15b05b53f1e9

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

Campaign

GHSA-p5cg-vcp7-xqhx

References

Credits

Amazon Inspector · finder

Detect & block this

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