Battle with Bots Prompts Mass Purge of Amazon, Apple Employee Accounts on LinkedIn

Read Time:5 Minute, 16 Second

On October 10, 2022, there were 576,562 LinkedIn accounts that listed their current employer as Apple Inc. The next day, half of those profiles no longer existed. A similarly dramatic drop in the number of LinkedIn profiles claiming employment at Amazon comes as LinkedIn is struggling to combat a significant uptick in the creation of fake employee accounts that pair AI-generated profile photos with text lifted from legitimate users.

Jay Pinho is a developer who is working on a product that tracks company data, including hiring. Pinho has been using LinkedIn to monitor daily employee headcounts at several dozen large organizations, and last week he noticed that two of them had far fewer people claiming to work for them than they did just 24 hours previously.

Pinho’s screenshot below shows the daily count of employees as displayed on Amazon’s LinkedIn homepage. Pinho said his scraper shows that the number of LinkedIn profiles claiming current roles at Amazon fell from roughly 1.25 million to 838,601 in just one day, a 33 percent drop:

The number of LinkedIn profiles claiming current positions at Amazon fell 33 percent overnight. Image: twitter.com/jaypinho

As stated above, the number of LinkedIn profiles that claimed to work at Apple fell by approximately 50 percent on Oct. 10, according to Pinho’s analysis:

Image: twitter.com/jaypinho

Neither Amazon or Apple responded to requests for comment. LinkedIn declined to answer questions about the account purges, saying only that the company is constantly working to keep the platform free of fake accounts. In June, LinkedIn acknowledged it was seeing a rise in fraudulent activity happening on the platform.

KrebsOnSecurity hired Menlo Park, Calif.-based SignalHire to check Pinho’s numbers. SignalHire keeps track of active and former profiles on LinkedIn, and during the Oct 9-11 timeframe SignalHire said it saw somewhat smaller but still unprecedented drops in active profiles tied to Amazon and Apple.

“The drop in the percentage of 7-10 percent [of all profiles], as it happened [during] this time, is not something that happened before,” SignalHire’s Anastacia Brown told KrebsOnSecurity.

Brown said the normal daily variation in profile numbers for these companies is plus or minus one percent.

“That’s definitely the first huge drop that happened throughout the time we’ve collected the profiles,” she said.

In late September 2022, KrebsOnSecurity warned about the proliferation of fake LinkedIn profiles for Chief Information Security Officer (CISO) roles at some of the world’s largest corporations. A follow-up story on Oct. 5 showed how the phony profile problem has affected virtually all executive roles at corporations, and how these fake profiles are creating an identity crisis for the businesses networking site and the companies that rely on it to hire and screen prospective employees.

A day after that second story ran, KrebsOnSecurity heard from a recruiter who noticed the number of LinkedIn profiles that claimed virtually any role in network security had dropped seven percent overnight. LinkedIn declined to comment about that earlier account purge, saying only that, “We’re constantly working at taking down fake accounts.”

A “swarm” of LinkedIn AI-generated bot accounts flagged by a LinkedIn group administrator recently.

It’s unclear whether LinkedIn is responsible for this latest account purge, or if individually affected companies are starting to take action on their own. The timing, however, argues for the former, as the account purges for Apple and Amazon employees tracked by Pinho appeared to happen within the same 24 hour period. Continue reading Battle with Bots Prompts Mass Purge of Amazon, Apple Employee Accounts on LinkedIn

nginx-mainline-3720221019155610.9e842022

Read Time:1 Minute, 0 Second

FEDORA-MODULAR-2022-03e951278d

Packages in this update:

nginx-mainline-3720221019155610.9e842022

Update description:

Security: processing of a specially crafted mp4 file by the ngx_http_mp4_module might cause a worker process crash, worker process memory disclosure, or might have potential other impact (CVE-2022-41741, CVE-2022-41742).

Feature: the “$proxy_protocol_tlv_…” variables.

Feature: TLS session tickets encryption keys are now automatically rotated when using shared memory in the “ssl_session_cache” directive.

Change: the logging level of the “bad record type” SSL errors has been lowered from “crit” to “info”. Thanks to Murilo Andrade.

Change: now when using shared memory in the “ssl_session_cache” directive the “could not allocate new session” errors are logged at the “warn” level instead of “alert” and not more often than once per second.

Bugfix: nginx/Windows could not be built with OpenSSL 3.0.x.

Bugfix: in logging of the PROXY protocol errors. Thanks to Sergey Brester.

Workaround: shared memory from the “ssl_session_cache” directive was spent on sessions using TLS session tickets when using TLSv1.3 with OpenSSL.

Workaround: timeout specified with the “ssl_session_timeout” directive did not work when using TLSv1.3 with OpenSSL or BoringSSL.

Read More

nginx-mainline-820220816123924.9edba152

Read Time:1 Minute, 1 Second

FEDORA-EPEL-MODULAR-2022-e97b3e0f82

Packages in this update:

nginx-mainline-820220816123924.9edba152

Update description:

Security: processing of a specially crafted mp4 file by the ngx_http_mp4_module might cause a worker process crash, worker process memory disclosure, or might have potential other impact (CVE-2022-41741, CVE-2022-41742).

Feature: the “$proxy_protocol_tlv_…” variables.

Feature: TLS session tickets encryption keys are now automatically rotated when using shared memory in the “ssl_session_cache” directive.

Change: the logging level of the “bad record type” SSL errors has been lowered from “crit” to “info”. Thanks to Murilo Andrade.

Change: now when using shared memory in the “ssl_session_cache” directive the “could not allocate new session” errors are logged at the “warn” level instead of “alert” and not more often than once per second.

Bugfix: nginx/Windows could not be built with OpenSSL 3.0.x.

Bugfix: in logging of the PROXY protocol errors. Thanks to Sergey Brester.

Workaround: shared memory from the “ssl_session_cache” directive was spent on sessions using TLS session tickets when using TLSv1.3 with OpenSSL.

Workaround: timeout specified with the “ssl_session_timeout” directive did not work when using TLSv1.3 with OpenSSL or BoringSSL.

Read More

nginx-mainline-3520221019155610.f27b74a8

Read Time:1 Minute, 0 Second

FEDORA-MODULAR-2022-2454736cf7

Packages in this update:

nginx-mainline-3520221019155610.f27b74a8

Update description:

Security: processing of a specially crafted mp4 file by the ngx_http_mp4_module might cause a worker process crash, worker process memory disclosure, or might have potential other impact (CVE-2022-41741, CVE-2022-41742).

Feature: the “$proxy_protocol_tlv_…” variables.

Feature: TLS session tickets encryption keys are now automatically rotated when using shared memory in the “ssl_session_cache” directive.

Change: the logging level of the “bad record type” SSL errors has been lowered from “crit” to “info”. Thanks to Murilo Andrade.

Change: now when using shared memory in the “ssl_session_cache” directive the “could not allocate new session” errors are logged at the “warn” level instead of “alert” and not more often than once per second.

Bugfix: nginx/Windows could not be built with OpenSSL 3.0.x.

Bugfix: in logging of the PROXY protocol errors. Thanks to Sergey Brester.

Workaround: shared memory from the “ssl_session_cache” directive was spent on sessions using TLS session tickets when using TLSv1.3 with OpenSSL.

Workaround: timeout specified with the “ssl_session_timeout” directive did not work when using TLSv1.3 with OpenSSL or BoringSSL.

Read More

nginx-mainline-3620221019155610.5e5ad4a0

Read Time:1 Minute, 0 Second

FEDORA-MODULAR-2022-d2cc9c919c

Packages in this update:

nginx-mainline-3620221019155610.5e5ad4a0

Update description:

Security: processing of a specially crafted mp4 file by the ngx_http_mp4_module might cause a worker process crash, worker process memory disclosure, or might have potential other impact (CVE-2022-41741, CVE-2022-41742).

Feature: the “$proxy_protocol_tlv_…” variables.

Feature: TLS session tickets encryption keys are now automatically rotated when using shared memory in the “ssl_session_cache” directive.

Change: the logging level of the “bad record type” SSL errors has been lowered from “crit” to “info”. Thanks to Murilo Andrade.

Change: now when using shared memory in the “ssl_session_cache” directive the “could not allocate new session” errors are logged at the “warn” level instead of “alert” and not more often than once per second.

Bugfix: nginx/Windows could not be built with OpenSSL 3.0.x.

Bugfix: in logging of the PROXY protocol errors. Thanks to Sergey Brester.

Workaround: shared memory from the “ssl_session_cache” directive was spent on sessions using TLS session tickets when using TLSv1.3 with OpenSSL.

Workaround: timeout specified with the “ssl_session_timeout” directive did not work when using TLSv1.3 with OpenSSL or BoringSSL.

Read More

nginx-1.22.1-1.fc37

Read Time:15 Second

FEDORA-2022-12721789aa

Packages in this update:

nginx-1.22.1-1.fc37

Update description:

Security: processing of a specially crafted mp4 file by the
ngx_http_mp4_module might cause a worker process crash, worker
process memory disclosure, or might have potential other impact
(CVE-2022-41741, CVE-2022-41742).

Read More