Which versions of getd-content-management are malicious?

The following npm versions of getd-content-management are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate getd-content-management if I installed it?

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

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

Yes — getd-content-management is associated with the IN-MAL-2026-005199, IN-MAL-2026-005200, GHSA-q9wx-x6cr-5wg7 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 getd-content-management 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 getd-content-management (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getd-content-management across your stack and pipelines.

Malicious package

getd-content-managementnpm

Malicious code in getd-content-management (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5465

Immediate action

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

npm uninstall getd-content-management

What this malware does

The unscoped package name 'getd-content-management' impersonates the legitimate @getd/* npm scope (acknowledged in the package's own README). On npm install, the postinstall.js lifecycle script collects host identifiers via os.hostname(), os.userInfo().username, os.platform(), process.cwd(), and CI-related environment variables (CI, BUILD_BUILDID, AGENT_NAME), and transmits them as query-string parameters in an HTTPS GET request to https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5 — a generic third-party request-capture service unrelated to any publisher infrastructure. Errors are silently swallowed so the installer sees no indication the call occurred. The combination of name-confusion against an existing scope and silent install-time beaconing of internal hostnames, user accounts, build paths, and CI agent identity to an attacker-controlled capture URL is operationally indistinguishable from a malicious typosquat regardless of how the README frames the behavior.

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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

44eb41541c340c710ad8afc366ab4642d3809d8d9afef53b99e3704b9dfb684b

efaa0ace9a4e74cb70a973143ccb7abd217de77d7fcd7bb588536de79c3d360c

0c0b8e667feb69ff5b0509e2d87c75ef2b178148960d0df0cb690d38e89ae291

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

Campaign

IN-MAL-2026-005199IN-MAL-2026-005200GHSA-q9wx-x6cr-5wg7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks getd-content-management-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