Which versions of typeorm-orbit are malicious?

The following npm versions of typeorm-orbit are flagged malicious: 0.2.27. Treat any of these as compromised.

How do I remediate typeorm-orbit if I installed it?

typeorm-orbit 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.

I already installed typeorm-orbit — how do I know if it already compromised me?

If typeorm-orbit 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.

Is typeorm-orbit part of a known attack campaign?

Yes — typeorm-orbit is associated with the GHSA-3359-gx7x-7392 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find typeorm-orbit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for typeorm-orbit (version 0.2.27). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typeorm-orbit across your stack and pipelines.

Malicious package

typeorm-orbitnpm

Malicious code in typeorm-orbit (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190786

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall typeorm-orbit

What this malware does

The package typeorm-orbit was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.2.27

Indicators of compromise (SHA-256)

a8e95331758f44ad97cde664359ec7ba72c0ad0c10caeaf02926a6007d23bb7f

f1ef9bad1469b974150720a17445c8403c0b0cd2bd2dbb393948afc47f102f95

46c9ef5ed62d33cc9debedbb55d0f2a71b282419536df72958cc4334ff5632b6

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for typeorm-orbit (version 0.2.27). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typeorm-orbit across your stack and pipelines.
If you installed it — respond
typeorm-orbit 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 typeorm-orbit 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 typeorm-orbit 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

No. typeorm-orbit on npm has been identified as a malicious package (version 0.2.27 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3359-gx7x-7392

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typeorm-orbit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring