NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

angular2-tesla-commonnpm

Advisory published Updated

angular2-tesla-common is a confirmed malicious npm package (MAL-2025-3138) that executes malicious code on install (malicious versions 99.99.100, 99.99.103, 999999999.9999999999.9999999999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angular2-tesla-common (npm)

MAL-2025-3138
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall angular2-tesla-common

What this malware does

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 'angular2-tesla-common' @ 99.99.103 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

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

Malicious versions

3 flagged
99.99.10099.99.103999999999.9999999999.9999999999

Indicators of compromise (SHA-256)

750e5a71820465f7842a06b6cbaa034cd7f4bf78fb9f20b44e5785088ae8b61a
70c304f6c9a78d04f8c2a1d7bdaa032abfca7d992df6ae1286285835cae8729d
7134a794a37bf8aae8607bb577adf8e9b11e74f9d080a48a1a4f935fb06a8b7b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for angular2-tesla-common (3 malicious versions).

  2. If you installed it — respond

    Remove angular2-tesla-common from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If angular2-tesla-common was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. angular2-tesla-common on npm has been identified as a malicious package (versions 99.99.100, 99.99.103, 999999999.9999999999.9999999999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xr85-54wg-xm89

References

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks angular2-tesla-common-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

angular2-tesla-common (npm) malicious package — MAL-2025-3138 | O3 Security