Missing verification of source of a communication channel in the default_bucket() function in Amazon SageMaker Python SDK V3 before 3.10.0 and V2 before 2.257.3 might allow remote actors to achieve code execution in the target SageMaker execution environment and obtain IAM credentials via pre-creation of a predictably named S3 bucket that the SDK uses without ownership validation.
To remediate this issue, users should upgrade to Amazon SageMaker Python SDK 3.10.0 (V3) or 2.257.3 (V2).
The npm package rs-lookout-sandbox-poc version 1.0.1 contains malicious code that, upon being loaded, automatically collects the local system username and sends it to an external third-party URL. Additionally, it performs reconnaissance on the AWS Instance Metadata Service by attempting to retrieve an IMDSv2 token and enumerating IAM role credentials associated with the host. These actions occur without any explicit invocation by the user.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.
Insertion of sensitive information into log file in AWS Tools for PowerShell before 5.0.306 might allow local users to recover an IAM user's cleartext AWS Management Console password from command output and log artifacts.
To remediate this issue, users should upgrade to version 5.0.306 or later. After upgrading, review PowerShell transcripts and log stores for previously disclosed passwords and rotate any affected IAM console passwords.
Missing authentication for critical function in the authentication dependency in Loom for AWS before 1.6.1 allowed remote actors to obtain super-admin authority over the agent control plane, including registering tool servers, reading stored integration credentials, and rewriting the IAM role policies attached to managed agent roles, via any request to the application API in a deployment where no identity provider is configured.
To remediate this issue, users should upgrade to version 1.6.1 or later.
Vvveb CMS versions prior to 1.0.8.6 contain a Server-Side Request Forgery (SSRF) vulnerability. The SSRF guard only resolves IPv4 addresses and does not inspect IPv6 addresses, allowing authenticated admin users to bypass private-range checks using IPv6 literals or domains with only AAAA records. This enables reading of internal-only services and cloud metadata, including IAM credentials. The issue is patched in version 1.0.8.6.
friendly-tools 0.2 carries the same Snowflake payload as friendly-greeting-tools. Its --run-demo option, described as a print-only demo, execs a gzip and base64 blob from friendly_greeting/main.py that reads the container session token at /snowflake/session/token, switches to ACCOUNTADMIN and copies a table into s3://pkusinski-external/ through a new storage integration.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (71b3a4955d5bd8448f0a56c843936702bb1f09eb8acbb9b468a5a337f8761b7f)
The package presents itself as 'Small greeting utilities' but ships two gzip+base64 embedded blobs (DEMO_EN, DEMO_ST) in main.py that are decoded and passed to exec() through the documented public API run_demo(). The decoded Python has no relation to greetings: it opens /snowflake/session/token to read the installer's Snowflake OAuth session token, calls snowflake.connector.connect with authenticator='oauth' and role='ACCOUNTADMIN', then issues DDL that creates an external S3 stage at s3://pkusinski-external/ using STORAGE_AWS_ROLE_ARN='arn:aws:iam::631484165566:role/pentests_s3_role', and runs COPY INTO @ROGUE.ROGUE.ext_stage FROM ROGUE.ROGUE.TEST_USERS to egress data to that non-first-party S3 bucket. When run_demo() is invoked in a Snowpark or Streamlit-in-Snowflake environment where /snowflake/session/token is provisioned, the installer's Snowflake credential is consumed under ACCOUNTADMIN to copy Snowflake table data to attacker-controlled storage. The obfuscation (gzip+base64+exec), the cover-story package description, and the hardcoded attacker S3 bucket and IAM role are consistent with a Snowflake-targeted data-theft payload.
## Source: kam193 (969afb49a1e59fa643e9d90d07745e3957906cc9603c4e5643e5760d5f254381)
The package contains obfuscated code to exfiltrate data from the environment, targeting primarily Snowflake databases and credentials to them. Some tracks suggest it may be part of a pentest.
---
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-friendly-greeting-tools
Reasons (based on the campaign):
- exfiltration-generic
- obfuscation
CVE-2026-55177 is a Server-Side Request Forgery (SSRF) vulnerability in dfpc-coe CloudTAK prior to version 13.10.0. Authenticated users with any token can exploit this flaw to make the CloudTAK server send arbitrary HTTP requests to internal network addresses without validation. This allows attackers to access sensitive internal services such as cloud instance metadata endpoints and loopback admin ports, potentially exposing temporary IAM credentials and other internal data. The vulnerability is fully patched in version 13.10.0.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (6457aa73ec15f68e06005977033aaba349467d40e3d406f0810684a43b74fcb5)
The package's preinstall script and its main entry (index.js) both perform identical credential-harvesting: they query the EC2 Instance Metadata Service (IMDSv2) at 169.254.169.254 for the identity document and IAM role security credentials, enumerate the entire process.env, and recursively read /var/run/secrets/ (Kubernetes service-account tokens and mounted secrets). The collected data is POSTed to a hardcoded attacker-controlled host at hrnmn.dd.h4x.tv (paths /save_instance_info_hook from preinstall and /save_instance_info_index from index.js). The destination is unrelated to any legitimate package purpose, there is no user configuration, and the behavior fires automatically on `npm install` via the preinstall lifecycle hook as well as on any `require()`/`import` of the package. The harvested material — temporary AWS IAM credentials, cloud instance identity, arbitrary environment variables (which routinely contain API keys, tokens, and database credentials in CI/build environments), and Kubernetes service-account tokens — grants immediate cross-service access to the installer's cloud and cluster resources.
## Source: ghsa-malware (07386b2d1e2efa71fd38c591953684c11302ad77f1c7943bd542b71fd83184e3)
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.
The npm package @hrmony/benefit-essenszuschuss (version 3.99.0) contains malicious code that, upon import, harvests cloud and container secrets from the host environment. It retrieves AWS IAM role credentials via the Instance Metadata Service (IMDSv2), collects environment variables, and reads Kubernetes secrets from the filesystem. This sensitive data is then exfiltrated to a hardcoded attacker-controlled endpoint. The package mimics an internal HR utility and includes an unpinned dependency, facilitating a dependency confusion attack. Systems with this package installed should be considered fully compromised.
The npm package @hrmony/app-gateway-templates (version 0.0.51) contains malicious code that exfiltrates sensitive AWS instance metadata, IAM credentials, environment variables, and Kubernetes secrets to an attacker-controlled endpoint. The package is a typosquat of 'harmony' and also pulls in additional attacker-controlled dependencies. Systems with this package installed should be considered fully compromised, and all secrets should be rotated immediately.
The npm package @hrmony/interfaces (version 0.99.0) contains malicious code that executes upon import or require. It collects sensitive AWS EC2 instance metadata, IAM role credentials, environment variables, and Kubernetes secrets, then exfiltrates this data to a hardcoded external server. This behavior is consistent with a dependency confusion attack. Systems with this package installed should be considered fully compromised, and all secrets should be rotated immediately.
The npm package @hrmony/benefit-internetzuschuss (version 1.99.0) contains malicious code that, upon import, sends AWS instance metadata, environment variables, Kubernetes secrets, and IAM credentials to a hardcoded external attacker-controlled server. This package masquerades as a German social-benefits helper but performs unauthorized credential harvesting. Systems with this package installed should be considered fully compromised.
The npm package @hrmony/cdk-constructs contains malicious code that executes immediately upon import or require. It harvests AWS EC2 instance metadata, including IAM role credentials, environment variables, and Kubernetes secrets, then exfiltrates this sensitive information to a hardcoded external server. The package is a typosquatting attempt targeting developers seeking legitimate AWS CDK constructs under the @harmony scope. It also installs an additional attacker-controlled dependency. Systems with this package installed should be considered fully compromised, and all secrets must be rotated immediately.
The npm package @hrmony/benefit-mobilitaet version 1.99.0 contains malicious code that, upon loading, contacts the EC2 Instance Metadata Service to retrieve sensitive instance identity and IAM role credentials. It also enumerates environment variables and Kubernetes secrets, then exfiltrates all collected data to a hardcoded attacker-controlled endpoint. This behavior indicates a dependency-confusion attack pattern and results in full compromise of any system running this package.
The npm package @hrmony/organisationsverwaltung version 7.99.0 contains malicious code that executes immediately upon import or require. It exfiltrates AWS IAM credentials, environment variables, and Kubernetes secrets by sending them to a hardcoded external server. This package is a dependency-confusion attack targeting an internal namespace. Systems with this package installed should be considered fully compromised, and all secrets should be rotated from a clean environment.
The npm package @hrmony/benefit-sachbezug (version 1.99.0) contains malicious code that executes upon import or require. It collects sensitive AWS EC2 instance metadata, IAM role credentials, environment variables, Kubernetes secrets, and user data, then sends this information to a hardcoded attacker-controlled endpoint. This behavior effectively compromises any system running the package, risking exposure of all stored secrets and keys.
The npm package @hrmony/pladddform-application version 2.99.0 contains malicious code that exfiltrates sensitive information from the host system. Upon loading, it executes routines that send installer-side secrets, AWS EC2 instance metadata including IAM role credentials, environment variables, and Kubernetes secrets to a hardcoded attacker-controlled endpoint. This package is likely a dependency confusion attack targeting internal package names. Any system with this package installed should be considered fully compromised.
The npm package '@hrmony/middlewares' is a malicious package designed to exfiltrate AWS instance metadata, IAM credentials, environment variables, and Kubernetes secrets to a hardcoded external server. It impersonates the legitimate '@harmony/middlewares' package by using a similar name. Installing or running this package compromises the host, potentially exposing all stored secrets and keys.
The npm package @hrmony/mailer-pladddform contains malicious code that executes immediately upon import. It harvests AWS IAM credentials, EC2 instance identity documents, Kubernetes ServiceAccount tokens, and other secrets from the host environment and exfiltrates them to a hardcoded attacker-controlled endpoint. The package does not provide any legitimate mailer functionality and appears to be a typosquatting or dependency confusion attack. Installation of this package compromises the host system, requiring immediate secret rotation and removal of the package.