Which versions of @actbase/node-server are malicious?

The following npm versions of @actbase/node-server are flagged malicious: 1.1.19. Treat any of these as compromised.

How do I remediate @actbase/node-server if I installed it?

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

If @actbase/node-server 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 @actbase/node-server part of a known attack campaign?

Yes — @actbase/node-server is associated with the GHSA-f6v4-qh83-p5x3 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/node-server 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 @actbase/node-server (version 1.1.19). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @actbase/node-server across your stack and pipelines.

Malicious package

@actbase/node-servernpm

Malicious code in @actbase/node-server (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190707

Immediate action

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

npm uninstall @actbase/node-server

What this malware does

The package @actbase/node-server 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.1.19

Indicators of compromise (SHA-256)

ceacf112643978a5df02bde5b330a1ca8fa00b2161404658fe5755bc54c1154b

a0017bb31e0f352229b8a7afc7305701c64b60033a69ccfec390385c507c6d85

bf4aaa916c9296632e7c0b20ab6a329aca31f36fe7b9c70905a1233e9c0f9557

011caaf07310f5faa801132320869c6279ecc9749b31a9f1e4aac5d3ded6c2fa

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

Campaign

GHSA-f6v4-qh83-p5x3

References

Credits

Amazon Inspector · finder

Detect & block this

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