singpass-myinfo-oidc-helpernpm
Advisory published Updated
singpass-myinfo-oidc-helper is a confirmed malicious npm package (MAL-2026-20062) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in singpass-myinfo-oidc-helper (npm)
What this malware does
singpass-myinfo-oidc-helper is a name-squatting package: it takes the unscoped form of the official Singpass/Myinfo SDK @govtechsg/singpass-myinfo-oidc-helper (Singapore's national digital identity), so a project that installs the name without its scope, or a build that resolves the unscoped name from the public registry, receives this package instead. Versions 0.0.1 and 0.0.2, published on 2026-11-17, declare a postinstall script that runs node postinstall.js, which sends an HTTPS GET to https://claim-test.ngrok.app/hello-world, an ngrok tunnel controlled by a third party. The request carries no payload, but it confirms the install to that party and discloses the installing machine's public IP address and the time of the install. The script never consumes the response, so the install can hang until the remote side closes the connection. index.js only prints a notice; the package describes itself as a "Security research placeholder". The 0.0.0-stage placeholder carries no install script and is not affected. Remove the package, depend on @govtechsg/singpass-myinfo-oidc-helper instead, and block claim-test.ngrok.app on build hosts.
The OpenSSF Package Analysis project identified 'singpass-myinfo-oidc-helper' @ 0.0.2 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for singpass-myinfo-oidc-helper (2 malicious versions).
If you installed it — respond
Remove singpass-myinfo-oidc-helper from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If singpass-myinfo-oidc-helper 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
Credits
- OpenSSF: Package Analysis · finder
- Robin Frehner, Protet · finder
Detect & block this
O3 blocks singpass-myinfo-oidc-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.