Which versions of upstartadmindashboard- are malicious?

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

How do I remediate upstartadmindashboard- if I installed it?

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

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

Yes — upstartadmindashboard- is associated with the GHSA-m873-wm98-r6vj 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 upstartadmindashboard- 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 upstartadmindashboard- (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 upstartadmindashboard- across your stack and pipelines.

Malicious package

upstartadmindashboard-npm

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

MAL-2026-2615

Immediate action

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

npm uninstall upstartadmindashboard-

What this malware does

The package is a malware. It exfiltrates system info to a hardcoded domain, collects sensitive data, and executes suspicious commands.

The package upstartadmindashboard- 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 'upstartadmindashboard-' @ 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)

8a4dc1b7f26cb51736d6bf86100d9be158286f54d6314360d877fdb581df57b6

cea0bf5ea5b6737e4c5255218610f471804a187d85633cc5562fcfaf644d437d

e0760e39fa3fc4d272de9fb78decddc3a25ae673efe12e9bff4e8d9f28ee5c55

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 upstartadmindashboard- (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 upstartadmindashboard- across your stack and pipelines.
If you installed it — respond
upstartadmindashboard- 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 upstartadmindashboard- 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 upstartadmindashboard- 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. upstartadmindashboard- 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-m873-wm98-r6vj

References

Credits

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

Detect & block this

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