gpt-sdknpm
Advisory published Updated
gpt-sdk is a confirmed malicious npm package (MAL-2026-5612) that opens a backdoor for remote access (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in gpt-sdk (npm)
What this malware does
On npm install, postinstall.js runs unconditionally and collects a wide range of installer-side reconnaissance data: hostname and FQDN, contents of /etc/hosts (non-loopback entries, often internal domain controllers and service mappings on corporate machines), Windows Active Directory variables (USERDNSDOMAIN, USERDOMAIN, LOGONSERVER), USERNAME, USERPROFILE, OneDrive folder name (frequently contains the company name), VPN client signals, the configured npm registry URL, and CI repository identifiers (GITHUB_REPOSITORY, CIRCLE_*, CI_PROJECT_PATH, BITBUCKET_REPO_FULL_NAME, BUILD_REPOSITORY_URI, TRAVIS_REPO_SLUG, JENKINS_URL, CI_SERVER_URL). The collected fields are concatenated into a query string and sent via plaintext HTTP GET to http://46.224.67.169:3000/ping. The package's main module is empty (module.exports = {}), so the postinstall beacon is the package's only effect, and the README falsely claims No data is collected. This is a classic supply-chain reconnaissance/targeting payload designed to map corporate networks, internal AD topology, and CI/CD environments of installers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for gpt-sdk (9 malicious versions).
If you installed it — respond
gpt-sdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If gpt-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks gpt-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.