Which versions of get-them-args are malicious?

The following npm versions of get-them-args are flagged malicious: 1.3.3. Treat any of these as compromised.

How do I remediate get-them-args if I installed it?

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

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

Yes — get-them-args is associated with the GHSA-6779-xgxr-9pcr 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 get-them-args 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 get-them-args (version 1.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging get-them-args across your stack and pipelines.

Malicious package

get-them-argsnpm

Malicious code in get-them-args (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191103

Immediate action

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

npm uninstall get-them-args

What this malware does

The package get-them-args 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.3.3

Indicators of compromise (SHA-256)

d70e3f04273d02fdaa9555197354a75aba13abe81a22763a353d47db93ce9b32

b280c2bc9fa8ed13e55f089006d920aa29961105c8f834abb8ca3a6ac463c428

1885f72a03b5b12ad9795b819da4d8cbd92b5985848b3f9a057afd389de5a8f8

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

Campaign

GHSA-6779-xgxr-9pcr

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks get-them-args-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