Which versions of @alfa.life.mapp/app.web are malicious?

The following npm versions of @alfa.life.mapp/app.web are flagged malicious: 99.0.10, 99.0.11, 99.0.13, 99.0.15, 99.0.16, 99.0.18. Treat any of these as compromised.

How do I remediate @alfa.life.mapp/app.web if I installed it?

Remove @alfa.life.mapp/app.web 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.

I already installed @alfa.life.mapp/app.web — how do I know if it already compromised me?

If @alfa.life.mapp/app.web 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 @alfa.life.mapp/app.web part of a known attack campaign?

Yes — @alfa.life.mapp/app.web is associated with the GHSA-68cm-x784-c9gw 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 @alfa.life.mapp/app.web 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 @alfa.life.mapp/app.web (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @alfa.life.mapp/app.web across your stack and pipelines.

Malicious package

@alfa.life.mapp/app.webnpm

Malicious code in @alfa.life.mapp/app.web (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3052

Immediate action

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

npm uninstall @alfa.life.mapp/app.web

What this malware does

The package @alfa.life.mapp/app.web 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 '@alfa.life.mapp/app.web' @ 99.0.15 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

6 flagged

99.0.1099.0.1199.0.1399.0.1599.0.1699.0.18

Indicators of compromise (SHA-256)

7ac6d0f18e7e372158e7106291eaed64ec2a6bee678aa033a2ef8f955396625d

91f3fb6ec9c5b34037ba56c8f1471d5d97b0535ae0bf06a02f990cd4d0631552

92d9870a3a07033d5aae11c1afa29814dbe482124cb0d1d791d8255c7b4e1be5

c688d0897b1c4e99a4bf43a3e0ed7cc022306334e2b2fc5c29dc45cb7ea4613c

d98755b751da7fb1c945ad5fd2ebfdb41021926306b112ef7e1942876bcff462

7d4cf8e1737663510f83e287e2d8e5a6cdfb2aad4056632e987ac5ca3fd9fc70

d31f4eb43fd465a585f96a6ae24d86885dcb21e0645e446d9831edce30250a9e

225853da23c9ff597131c8172ad7fbad7b77641356913b62b0014b166145db95

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @alfa.life.mapp/app.web (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @alfa.life.mapp/app.web across your stack and pipelines.
If you installed it — respond
Remove @alfa.life.mapp/app.web 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.
Did it already run?
If @alfa.life.mapp/app.web 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 @alfa.life.mapp/app.web 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. @alfa.life.mapp/app.web on npm has been identified as a malicious package (versions 99.0.10, 99.0.11, 99.0.13, 99.0.15, 99.0.16, 99.0.18 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-68cm-x784-c9gw

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @alfa.life.mapp/app.web-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.

Malware detection Runtime egress monitoring