Which versions of upstartdr are malicious?

The following npm versions of upstartdr are flagged malicious: 99.99.1. Treat any of these as compromised.

How do I remediate upstartdr if I installed it?

upstartdr 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 upstartdr — how do I know if it already compromised me?

If upstartdr 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 upstartdr part of a known attack campaign?

Yes — upstartdr is associated with the GHSA-7vv7-22qp-3mj7 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 upstartdr 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 upstartdr (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upstartdr across your stack and pipelines.

Malicious package

upstartdrnpm

Malicious code in upstartdr (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2618

Immediate action

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

npm uninstall upstartdr

What this malware does

Package is malware. It steals credentials, system info, and exfiltrates data to a remote server via a postinstall script. High confidence.

The package upstartdr 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.

The OpenSSF Package Analysis project identified 'upstartdr' @ 99.99.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.1

Indicators of compromise (SHA-256)

56de133ae827b810b8df2dc0491bcb0a94d78fefc0a148b382f72ede67a3a04d

6eb8bc38754abd1d12d677bcea56ca7680f3c899cebf4b948e39b6ee6fd8642a

d6563c7981cb66eadd2e5e9afe7b2957682f62c767cdfbe4258048c628758525

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 upstartdr (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upstartdr across your stack and pipelines.
If you installed it — respond
upstartdr 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 upstartdr 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 upstartdr 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. upstartdr on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7vv7-22qp-3mj7

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks upstartdr-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