Which versions of upstartportal are malicious?

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

How do I remediate upstartportal if I installed it?

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

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

Yes — upstartportal is associated with the GHSA-q4fh-w299-f753 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 upstartportal 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 upstartportal (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 upstartportal across your stack and pipelines.

Malicious package

upstartportalnpm

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

MAL-2026-2620

Immediate action

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

npm uninstall upstartportal

What this malware does

Collects system info, reads sensitive files, and exfiltrates data to a suspicious host. Multiple YARA matches confirm malicious intent.

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

4b2a33bb664793479de0ef40d34e74655b514c573399cd553aff56564bf0d87f

c9846f45863c462296951028bddee77aba25fb02cb7b5d41c40e31d493e00366

932dee0dcf84fc1044efb1ec35950d6102fcbb5122f26cca5e2b1f13eb599729

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 upstartportal (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 upstartportal across your stack and pipelines.
If you installed it — respond
upstartportal 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 upstartportal 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 upstartportal 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. upstartportal 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-q4fh-w299-f753

References

Credits

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

Detect & block this

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