cdk-sagemaker-notebook-workflownpm
Malicious code in cdk-sagemaker-notebook-workflow (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
The package declares a preinstall hook (node index.js) in package.json that fires automatically on npm install. The script collects os.hostname(), os.userInfo().username, os.platform(), current working directory, home directory, the contents of /etc/passwd (fs.readFileSync('/etc/passwd', 'utf8')), and the first 30 entries of process.env (Object.entries(process.env).slice(0, 30)), then POSTs the JSON payload to https://3nrgzlqwix6erldow0s0kttsojuai36s.oastify.com/greengrass/<execId> — a Burp Collaborator-style OAST host. Bulk env-var enumeration on CI runners typically captures AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, and similar credentials. The package name impersonates the AWS CDK construct namespace (cdk-sagemaker-notebook-workflow) and the README contains the string Takeover By l0bo, confirming attacker intent. This is an unambiguous install-time credential and host-data exfiltrator with a typosquat lure on the AWS CDK ecosystem.
The OpenSSF Package Analysis project identified 'cdk-sagemaker-notebook-workflow' @ 2.0.5 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cdk-sagemaker-notebook-workflow (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cdk-sagemaker-notebook-workflow across your stack and pipelines.
If you installed it — respond
cdk-sagemaker-notebook-workflow 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 cdk-sagemaker-notebook-workflow 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 cdk-sagemaker-notebook-workflow 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks cdk-sagemaker-notebook-workflow-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.