Which versions of @trigo/atrix-pubsub are malicious?

The following npm versions of @trigo/atrix-pubsub are flagged malicious: 4.0.3. Treat any of these as compromised.

How do I remediate @trigo/atrix-pubsub if I installed it?

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

If @trigo/atrix-pubsub 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 @trigo/atrix-pubsub part of a known attack campaign?

Yes — @trigo/atrix-pubsub is associated with the GHSA-6fj4-3x5p-5v33 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 @trigo/atrix-pubsub 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 @trigo/atrix-pubsub (version 4.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/atrix-pubsub across your stack and pipelines.

Malicious package

@trigo/atrix-pubsubnpm

Malicious code in @trigo/atrix-pubsub (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190828

Immediate action

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

npm uninstall @trigo/atrix-pubsub

What this malware does

The package @trigo/atrix-pubsub 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

4.0.3

Indicators of compromise (SHA-256)

87baac0813606db986d8dabbee359e8596bad6afb9f8f6c8d6f8312eac8b3936

774898dc5178ad4bd2128a0ec966ceb51a9cc46c9884a0618869d7525c96260c

c39e850c95162b27bfded34612ff18ff1939adc3d56bdb02d96f1d80ba153003

c8f4cb22a0485dd53bd13b1ca63f2a9c32e253aa58fe816cf72e8c3bea633180

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

Campaign

GHSA-6fj4-3x5p-5v33

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @trigo/atrix-pubsub-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