Which versions of upstartapplicationstatus are malicious?

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

How do I remediate upstartapplicationstatus if I installed it?

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

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

Yes — upstartapplicationstatus is associated with the GHSA-9hj7-rh99-qm24 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 upstartapplicationstatus 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 upstartapplicationstatus (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 upstartapplicationstatus across your stack and pipelines.

Malicious package

upstartapplicationstatusnpm

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

MAL-2026-2616

Immediate action

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

npm uninstall upstartapplicationstatus

What this malware does

Package is malware. Collects and exfiltrates sensitive info (SSH keys, credentials, env vars) via insecure HTTPS/HTTP after install.

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

42d35dfc281180cb917a1f008e3a33ea2a734f2442a27ca7ad334cd05e5e84e6

8c81f1ff86d1d941f9501d62238c0eed0e8c6e9463fd5d416a6f4c3ab501e3a9

e154270d6b3540f095f5fc77ab1167448e967009cbb719f6fc087c32fadce15f

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 upstartapplicationstatus (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 upstartapplicationstatus across your stack and pipelines.
If you installed it — respond
upstartapplicationstatus 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 upstartapplicationstatus 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 upstartapplicationstatus 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. upstartapplicationstatus 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-9hj7-rh99-qm24

References

Credits

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

Detect & block this

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