Which versions of upstart-lending-status are malicious?

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

How do I remediate upstart-lending-status if I installed it?

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

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

Yes — upstart-lending-status is associated with the GHSA-w3xp-4hxm-c484 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 upstart-lending-status 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 upstart-lending-status (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 upstart-lending-status across your stack and pipelines.

Malicious package

upstart-lending-statusnpm

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

MAL-2026-2611

Immediate action

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

npm uninstall upstart-lending-status

What this malware does

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

The package upstart-lending-status 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 'upstart-lending-status' @ 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)

9409aa80959df521637ea5c0316652c74f76474b4824e1737376553d4ba035c3

33507bc8de1cc8a2f11e026c56e5d1a66f79b5679abd9b470501e0332d7f3ca0

627a2802a53ad7eb751fcac4b0a43245c6b0bf9e667db77051758b24d8bc4d96

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 upstart-lending-status (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 upstart-lending-status across your stack and pipelines.
If you installed it — respond
upstart-lending-status 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 upstart-lending-status 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 upstart-lending-status 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. upstart-lending-status 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-w3xp-4hxm-c484

References

Credits

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

Detect & block this

O3 blocks upstart-lending-status-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