Which versions of @actbase/native are malicious?

The following npm versions of @actbase/native are flagged malicious: 0.1.32. Treat any of these as compromised.

How do I remediate @actbase/native if I installed it?

@actbase/native 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 @actbase/native — how do I know if it already compromised me?

If @actbase/native 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.

Is @actbase/native part of a known attack campaign?

Yes — @actbase/native is associated with the GHSA-9h93-h6x9-6j4j 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 @actbase/native across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @actbase/native (version 0.1.32).

Part of a larger attack: @actbase published 15 malicious packages. See the full campaign →

Malicious package

@actbase/nativenpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@actbase/native is a confirmed malicious npm package (MAL-2025-191178) that steals credentials and exfiltrates sensitive data (malicious version 0.1.32). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @actbase/native (npm)

MAL-2025-191178

Immediate action

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

npm uninstall @actbase/native

What this malware does

The package @actbase/native 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

0.1.32

Indicators of compromise (SHA-256)

25e50e6942ddbe54ed3cdd6f5e36fabcf25cd195232e4a97e66e8159e569d922

eb78c3f4eb3df2581ae53c6b6c46aa1d14c7a6027fa4f248b1e2b15763763edf

328d7b0db77bbbc8012f6aee1eec6c2c15d1fec187573be00958308bceaf3b13

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-9h93-h6x9-6j4j

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @actbase/native-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

Explore

All malware advisories How O3 detects malware Vulnerability database